Deployment notes

Please update this page if the deployment steps change. Otherwise your colleagues will be very confused if they have never worked on the website before. Dev karma is real.

1. SSH into the EC2 instance. If you do not have access, nor have the means to ask someone for access, you probably aren't supposed to be deploying anything.

   • If you instead just want your proposed change implemented, please open a PR and ping somebody at our Community Slack
   • If you are actually on the ILF tech team, maybe you never had anything to do with the website previously but have sadly been arrowed to do something, please ping Hui Jing or Alex in the tech-team Slack channel

2. Navigate to the document root folder

3. Pull the latest changes

   git pull
   

4. If the change involves core or module updates, run the database update script and clear cache, otherwise just clearing cache will do

   ./vendor/bin/drush updatedb
   ./vendor/bin/drush cr
   

5. If you run into errors related to being unable to access/make changes to the CSS or JS files/folder, it's because Git reset the folder permissions (and the main site maintainer hasn't figured out the right way to do things yet 乁⁠(⁠ ⁠•⁠_⁠•⁠ ⁠)⁠ㄏ), fix the permissions on the css and js folders

   sudo chown -R USER_NAME:GROUP_NAME /var/www/html/web/sites/default/files/css
   sudo chown -R USER_NAME:GROUP_NAME /var/www/html/web/sites/default/files/js
   

6. Double check that the website is still running and that nothing exploded.