Apache 2.4, PHP 7.0, MySQL 5.6, Node.js, npm
For development code standards see https://github.com/DontPanicDigital/standards.
Run this command
git config branch.autosetuprebase always
It will setup your local repository to use rebase instead of merge on git pull. Rebase is better because merge creates ugly and confusing patterns. Merge should be used only between different branches, not within a single branch.
Also, if you use PHPStorm git functionality (which you should!), set it up to use rebase on pull too.
Copy /.htaccess.dist to a new file /htaccess and edit it.
Copy /app/config/parameters.neon.dist to a new file /app/config/parameters.neon and edit it.
Copy /react/config/index.js.dist to a new file /react/config/index.js and edit it:
- Set host to match your localhost setup.
Whenever you need to change something in the database (for example you create or change some entity), you have to define new migrations file.
To learn more about doctrine/migrations, see http://docs.doctrine-project.org/projects/doctrine-migrations/en/latest/index.html.
To generate new migrations file, run php www/web/index.php migrations:generate.
After generating new file, edit it to run desired SQL code.
Don't forget to implement both up() and down() methods to ensure that the new changes can be reverted.
The most common reason to create new migrations is, when you create or edit some entity.
Run php www/web/index.php orm:schema-tool:update --dump-sql to get SQL code. Then copy it to the new migrations file.
Then implement down() method to revert schema back to original state.
To run new migrations, run php www/web/index.php migrations:migrate. This command is also called automatically when running composer install.