Closed Bug 1380679 Opened 6 years ago Closed 6 years ago
Document how to deploy changes to Orange
Geoff was asking how to deploy changes and I realised it's not documented anywhere. We also spotted that he was missing sudoers access (filed bug 1380666 for that) - which would be good to include in the instructions too.
I've gone through the previous deployment workflow from bash history and simplified it slightly (as part of moving to openresty I made the UI static assets be served directly from the source directory, which means we can skip the sync step; also it's unnecessary to do all the `sudo su - <user>` steps, everything can be run from the current user). I've added it here: https://wiki.mozilla.org/Auto-tools/Projects/OrangeFactor#Deploying I also noticed the now unused deploy.sh script still exists in the repo, so removed it and updated the README to point to the wiki: remote: https://hg.mozilla.org/automation/orangefactor/rev/9c46e81fa1243ecf4354a707f56701141c269b7c remote: https://hg.mozilla.org/automation/orangefactor/rev/db72daf6f7022241141bcc450dcfc85b1023446b
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.