The question:
Following this interesting question from Fabian: Reasons to setup cronjob for setup:cron:run and update/cron.php on a deployed production system?
I’ve discovered that my Magento 2 installed via GitHub does not have the update/cron.php file.
Edit: my install does not have an update folder at all.
Where does that file come from ? How can I get it when installing from GitHub ?
The Solutions:
Below are the methods you can try. The first solution is probably the best. Try others if the first one doesn’t work. Senior developers aren’t just copying/pasting – they read the methods carefully & apply them wisely to each case.
Method 1
I read the doc a second time (http://devdocs.magento.com/guides/v2.0/config-guide/cli/config-cli-subcommands-cron.html) and here’s the answer:
If you cloned the GitHub repository you don’t have an update directory
and errors result if you run magento setup:cron:run. These cron jobs
work in the Web Setup Wizard, which contributing developers cannot use
for installing or updating the Magento application or components.
So basically people using Magento 2 from GitHub can’t use the Web Setup Wizard to install/update Magento components, which is painful if let’s say you installed M2 via GitHub and wanna switch to Web Setup Wizard after some point.
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0