If your project programmatically creates files or allows users to upload files via a user form or a custom form, you should run the normalise-access task. It also lets developers set these processes to be executed in the future.
vendor/bin/sake dev/cron Server configuration The Queued Jobs module provides a framework for SilverStripe developers to define long running processes that should be run as background tasks. Introducing Composer.
Here is one way to download and set up a Silverstripe website from a live server. Then execute the crontask controller, it's preferable you do this via the CLI since that is how the server will execute it. Connect to the live server through ftp Download all the files from the server to your local development folder In a default installation of SilverStripe, your project directory is called mysite/, and lives in the project root. The process of creating a local development version of a Silverstripe site would be very similar to that of deploying a site to a live server. At this stage, you could in theory run your project in SilverStripe 4. Up and Running: Setting up a local SilverStripe dev environment Installing a local web server. If your project was upgraded from a Silverstripe CMS 3 project, you should minimally run the migrate-folders subtask. Run vendor/bin/sake dev/build flush=1 to make SilverStripe aware of the new module. This asynchronous processing allows users to continue using the system while long running tasks proceed when time permits.
The --dev flag is optional, and can be used to add a couple modules which are useful for SilverStripe development: The behat-extension module allows running Behat integration tests The docsviewer module will let you preview changes to the project documentation The buildtools module which … This is a good point to commit your changes to your source control system before moving on to the next step.
Step 7 - Update project structure (optional) # SilverStripe 4 introduces a new recommended project structure . Because the code layer is detached from the UI, a given project can …
Your theme directory, however, will be located one level deeper, under the themes/ folder.