Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I do it with symlinks and completely separate release directories. Ie, a deployment involves cloning the entire project into a new directory, building the virtualenv inside that, then switching the "production" symlink to point at that directory.</p> <p>My layout is basically </p> <pre><code>/var/www/myapp/ uploads/ tmp/ releases/ 001/myapp/ 002/myapp/ 003/myapp/ ve/ ...etc in each release directory... myapp # symlink to releases/003/myapp/ </code></pre> <p>So, when I deploy to production, my deployment scripts rsync a completely fresh copy to <code>/var/www/myapp/releases/004/myapp/</code>, build a virtualenv in there, install all the packages into it, then </p> <pre><code>rm -f /var/www/myapp/myapp ln -s /var/www/myapp/releases/004/myapp/ /var/www/myapp/myapp </code></pre> <p>My actual deployment script is a little more complicated as I also make sure to keep the previous release around and marked so if I notice that something is really broken, rolling back is just a matter of switching the symlink to point back at the previous one. (some extra work is also necessary to clean up old, unused releases if you are worried about the disk space).</p> <p>Every external reference (in apache config files or wsgi files or whatever) point at libraries and binaries in the virtualenv as <code>/var/www/myapp/myapp/ve/</code>. I also shun the use of <code>source ve/bin/activate</code> and instead point at the full path in config files and I edit <code>manage.py</code> to use <code>#!ve/bin/python</code> so I can run commands with <code>./manage.py whatever</code> and it will always work without me having to remember if I've activated the right virtualenv.</p>
    singulars
    1. This table or related slice is empty.
    1. POdjango + virtualenv = atomic upgrade - is it possible?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USthraxil
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POdjango + virtualenv = atomic upgrade - is it possible?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTechnically between 'rm' and 'ln' Apache could fail a request because WSGI script is missing. Slightly safer method is to have simple WSGI script outside of package and have it setup sys.path to somewhere in real location of project and have it import a module from there which sets up actual WSGI application. When updating, create new WSGI script file with new path in it and 'mv' it into place of existing one. The 'mv' command should be atomic as far as file system change.
      singulars
      1. PO
      1. USGraham Dumpleton
    2. COGraham, that's a great idea. I'll see if I can work that into my process. I wasn't fooling myself into thinking that my approach is strictly atomic, just a large improvement over having the app broken for the duration of the virtualenv build.
      singulars
      1. PO
      1. USthraxil
    3. COActually, the `rm` isn't necessary at all. You can use `ln -sf` to force the removal of the previous existing symlink.
      singulars
      1. PO
      1. USire_and_curses
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload