Note that there are some explanatory texts on larger screens.

plurals
  1. POOrganising project files for a Python webapp with database functionality
    text
    copied!<p>I'd like some advice on how to organise the files for a database-driven web application.</p> <p>The main components of the project are:</p> <ul> <li>An SQLite database</li> <li>A web application written with the Pyramid framework, which reads from the database</li> <li>A set of Python applications which download data and add it to the database</li> <li>Documentation</li> </ul> <p>I'd like to track all source files of all the components (including the documentation) using git.</p> <p>Does the following seem like a good structure for the project?</p> <pre><code>Main_Project_Directory +-- virtualenv | +-- bin, lib, include, man | +-- PyramidApplication | | +-- setup.py | | +-- development.ini | | +-- Application | | | +-- __init__.py | | | +-- ... | | +-- ... | +-- DatabaseWritingApp1 | | +-- __init__.py | | +-- ... | +-- DatabaseWritingApp2 | | +-- __init__.py | | +-- ... | +-- database.sqlite +-- documentation </code></pre> <p>How should I initialise git repositories here? Would it be good to have one git repository in the top directory to track the pyramid app, other apps, and the documentation? Or would multiple git repositories be preferable? I am the sole developer on this project.</p> <p>Also, is there some file in the virtualenv which lists all the installed packages and their versions, so that the bin, lib, etc. directories can be rebuilt from it? If so, would it be good to include that file in a git repository so that the virtualenv can easily be rebuilt after a pull?</p> <p>Thanks for any assistance.</p>
 

Querying!

 
Guidance

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