Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix setup of production and staging instances so that OC sysadmins can update to latest branches #757

Open
rdhyee opened this issue Oct 25, 2019 · 0 comments

Comments

@rdhyee
Copy link
Collaborator

rdhyee commented Oct 25, 2019

Today, I had to futz around with the production server to update it to ekansa/open-context-py at production. Some issues to resolve are the naming of remote branches on the instances and some file ownership issues. Let me record some things I had to do to remind myself what I will need to fix

   73  git remote add upstream [email protected]:ekansa/open-context-py.git
   74  git fetch upstream
   76  git checkout -b production origin/production
   78  sudo -u www-data git checkout -b production origin/production
   86  sudo chown -R www-data:www-data /var/oc-venv
   95  cd /opt/ocweb
   97  sudo chown www-data:www-data *
   98  cd /var/oc-venv
   99  sudo pkill uwsgi
  100  sudo -u www-data /var/oc-venv/.venv/bin/uwsgi --http :8000 --ini /opt/ocweb/uwsgi_oc.ini
  101  sudo /etc/init.d/nginx restart
  106  tail -f /opt/ocweb/access-ssl.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant