@@ -43,20 +43,7 @@ Now install additional dependencies locally:
4343 pip install -r requirements-test.txt # for running tests
4444
4545
46- That's it for the setup. Now to initialize the DB:
47-
48- First run the commands from :ref: `db-setup `. Then
49-
50- .. code-block :: bash
51-
52- cd mygpo
53- python manage.py migrate
54-
55- ..and here we go:
56-
57- .. code-block :: bash
58-
59- python manage.py runserver
46+ That's it for the setup.
6047
6148
6249Configuration
@@ -72,9 +59,35 @@ For a development configuration you will probably want to use the following
7259 echo postgres://mygpo:mygpo@localhost/mygpo > envs/local/DATABASE_URL
7360 echo True > envs/local/DEBUG
7461
62+ On an Debian/Ubuntu based system, you can perform this configuration with
63+
64+ .. code-block :: bash
65+
66+ make dev-config
67+
7568 See :ref: `configuration ` for further information.
7669
7770
71+ Database Initialization
72+ -----------------------
73+
74+ Now to initialize the DB:
75+
76+ First run the commands from :ref: `db-setup `. Then
77+
78+ .. code-block :: bash
79+
80+ cd mygpo
81+ envdir envs/local python manage.py migrate
82+
83+ ..and here we go:
84+
85+ .. code-block :: bash
86+
87+ envdir envs/local python manage.py runserver
88+
89+
90+
7891 Accessing the dev server from other devices
7992-------------------------------------------
8093
@@ -84,7 +97,7 @@ runserver command of manage.py, like this:
8497
8598.. code-block :: bash
8699
87- python manage.py runserver 0.0.0.0:8000
100+ envdir envs/local python manage.py runserver 0.0.0.0:8000
88101
89102 Beware, though, that this will expose the web service to your all networks
90103that your machine is connected to. Apply common sense and ideally use only
@@ -101,22 +114,22 @@ commands regularly on your development machine:
101114
102115.. code-block :: bash
103116
104- python manage.py update-categories
105- python manage.py update-toplist
106- python manage.py update-episode-toplist
117+ envdir envs/local python manage.py update-categories
118+ envdir envs/local python manage.py update-toplist
119+ envdir envs/local python manage.py update-episode-toplist
107120
108- python manage.py feed-downloader
109- python manage.py feed-downloader < feed-url> [...]
110- python manage.py feed-downloader --max < max-updates>
111- python manage.py feed-downloader --random --max < max-updates>
112- python manage.py feed-downloader --toplist --max < max-updates>
113- python manage.py feed-downloader --update-new --max < max-updates>
121+ envdir envs/local python manage.py feed-downloader
122+ envdir envs/local python manage.py feed-downloader < feed-url> [...]
123+ envdir envs/local python manage.py feed-downloader --max < max-updates>
124+ envdir envs/local python manage.py feed-downloader --random --max < max-updates>
125+ envdir envs/local python manage.py feed-downloader --toplist --max < max-updates>
126+ envdir envs/local python manage.py feed-downloader --update-new --max < max-updates>
114127
115128 or to only do a dry run (this won't do any web requests for feeds):
116129
117130.. code-block :: bash
118131
119- python manage.py feed-downloader --list-only [other parameters]
132+ envdir envs/local python manage.py feed-downloader --list-only [other parameters]
120133
121134
122135 Maintaining publisher relationships with user accounts
@@ -127,7 +140,7 @@ To set a user as publisher for a given feed URL, use:
127140.. code-block :: bash
128141
129142 cd mygpo
130- python manage.py make-publisher < username> < feed-url> [...]
143+ envdir envs/local python manage.py make-publisher < username> < feed-url> [...]
131144
132145
133146 Web-Server
@@ -138,7 +151,7 @@ directory with
138151
139152.. code-block :: bash
140153
141- python manage.py runserver
154+ envdir envs/local python manage.py runserver
142155
143156 If you want to run a production server, check out `Deploying Django
144157<https://docs.djangoproject.com/en/dev/howto/deployment/> `_.
0 commit comments