1 | Installing Remit |
---|
2 | ================ |
---|
3 | |
---|
4 | Development installs |
---|
5 | -------------------- |
---|
6 | |
---|
7 | Installing Remit on a Linux machine for development purposes is quite straightforward: |
---|
8 | |
---|
9 | 1. Create and enter a virtualenv for Remit |
---|
10 | 2. Install Remit and its dependencies |
---|
11 | 3. Create the config files and initialize the database |
---|
12 | 4. Run the dev server |
---|
13 | |
---|
14 | As a sequence of commands, this is:: |
---|
15 | |
---|
16 | virtualenv --prompt="(venv/remit)" remit-venv # create the virtualenv |
---|
17 | cd remit-venv/ # enter it (filesystem) |
---|
18 | . bin/activate # enter it (environment) |
---|
19 | pip install --editable git+/mit/remit/remit.git#egg=remit # install Remit |
---|
20 | cd src/remit/remit/ # change into the main source directory |
---|
21 | ./setting/init-dev.sh # set up for development |
---|
22 | ./runserver 8006 # run the dev server |
---|
23 | |
---|
24 | Production installs |
---|
25 | ------------------- |
---|
26 | |
---|
27 | For production installs of Remit, a number of additional factors become important: |
---|
28 | |
---|
29 | - properly integrating with the web server (and not just using Django's server) |
---|
30 | - using appropriate email addresses (and actually sending mail) |
---|
31 | - using the group's real account structure |
---|
32 | |
---|
33 | As a result, the installation process is much more involved: |
---|
34 | |
---|
35 | 1. At heart, Remit is just another Django application. Do whatever you normally need to do to install a Django application and connect it to your web server. |
---|
36 | 2. Create settings/local.py containing: |
---|
37 | |
---|
38 | - ``SECRET_KEY`` |
---|
39 | - ``ADMINS`` |
---|
40 | - Database configuration |
---|
41 | - ``SERVER_EMAIL`` |
---|
42 | - ``SITE_URL_BASE`` -- full URL (including protocol and hostname; used in emails) |
---|
43 | - Any other settings you want |
---|
44 | |
---|
45 | 3. Create settings/local_after.py (possibly empty) |
---|
46 | 4. Run "./manage.py syncdb && ./manage.py migrate" to set up the database |
---|
47 | 5. Run "./util/setup.py" to install the basic accounts (Assets, Expenses, Income, plus some common GLs) |
---|
48 | 6. Run "./util/add_accounts" to add new accounts |
---|
49 | |
---|
50 | - First argument: path to the base account --- for example, "Accounts.Assets" |
---|
51 | - Standard input: accounts to add, separated by newline (to specify account numbers, add a tab followed by the account number) |
---|
52 | |
---|
53 | 7. Use the admin interface to set up appropriate BudgetTerm(s) |
---|
54 | 8. Make sure that the remit/media/ directory gets served to the web as media |
---|