# when asked whether you want to execute the recipes for some of the components,
# when asked whether you want to execute the recipes or install plugins for some of the components,
# you can safely type 'n' (for 'no').
# you can safely type 'n' (for 'no').
yarn set version stable
yarn set version 3.4.1
# delete yarn.lock as it might contain restrictive packages from a different context
# delete yarn.lock as it might contain restrictive packages from a different context
rm yarn.lock
yarn up
yarn install
yarn install
yarn dev
yarn dev
# you can safely ignore any "warning" mentioned by yarn dev
# you can safely ignore any "warning" mentioned by yarn dev
sudo chmod -R 777 .
sudo touch .env
sudo chown -R www-data: var/ .env config/
~~~~
~~~~
In your web server configuration, ensure you allow for the interpretation of .htaccess (`AllowOverride all` and `Require all granted`), and point the `DocumentRoot` to the `public/` subdirectory.
In your web server configuration, ensure you allow for the interpretation of .htaccess (`AllowOverride all` and `Require all granted`), and point the `DocumentRoot` to the `public/` subdirectory.
@ -77,8 +82,7 @@ Once the above is ready, enter the **main/install/index.php** and follow the UI
After the web install process, change the permissions back to a reasonably safe state:
After the web install process, change the permissions back to a reasonably safe state:
~~~~
~~~~
chmod -R 755 .
chown -R root .env config/
chown -R www-data: public/ var/
~~~~
~~~~
## Quick update
## Quick update
@ -91,6 +95,9 @@ composer update
# Database update
# Database update
php bin/console doctrine:schema:update --force
php bin/console doctrine:schema:update --force
# Clean Symfony cache
php bin/console cache:clear
# js/css update
# js/css update
yarn install
yarn install
yarn dev
yarn dev
@ -113,7 +120,7 @@ This issue rarely happens, though.
If you have it installed in a dev environment and feel like you should clean it up completely (might be necessary after changes to the database), you can do so by:
If you have it installed in a dev environment and feel like you should clean it up completely (might be necessary after changes to the database), you can do so by:
* Removing the `.env.local`
* Removing the `.env` file
* Load the {url}/main/install/index.php script again
* Load the {url}/main/install/index.php script again
The database should be automatically destroyed, table by table. In some extreme cases (a previous version created a table that is not necessary anymore and creates issues), you might want to clean it completely by just dropping it, but this shouldn't be necessary most of the time.
The database should be automatically destroyed, table by table. In some extreme cases (a previous version created a table that is not necessary anymore and creates issues), you might want to clean it completely by just dropping it, but this shouldn't be necessary most of the time.