Table of Contents exclude Contents
| exclude | Contents |
|---|
Overview
This document describes the soup-to-nuts engineering process for creating and maintaining a "cspace_django_project" Project for your institution. This process is the culmination of some months of experimentation and development at UCB, and what you see here is really the tip of the iceberg. The many details of how this process came about, its motivations, and its justification, are here.
...
- CSpace-Django webapps - setting up a production environment using Apache
- CSpace-Django webapps - setting up configuration for your project
Pushing your spiffy revised project to a Dev or Production Server
Let's suppose your project is already deployed and running (see the step above). You have made some wonderful fixes and improvements and you need to update the code on the server to the latest version. Assuming your changes have been pushed up to the master branch of your institutions repo, you need only pull the code changes for that release into the deployed project's repo on the target server (keeping any local mods via git stash) and restarting Apache:
sshin to the servercd /usr/local/share/django/my_project- (sudo git stash) # needed if you have local modifications to the code that you want to preserve.
sudo git pull -v- make any local mods required: e.g. update/add configuration file(s): "
sudo vi config/webapp.cfg" - (sudo git stash apply) # needed only if you stashed local changes above
sudo manage.py collectstaticsudo service httpd graceful
...