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 ?

1 Answer 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.

  • 4
    This is the correct answer. You should not start projects based on GitHub. It does not work with updates properly. Think of it like a library to use. you would not develop within the library tree but just include the library as a dependency Commented Sep 2, 2016 at 17:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.