You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> **Note** The `pip install` step can take a couple of minutes. Patience, patience! But if it takes more than 5 minutes, something is wrong. Ask your coach.
188
+
187
189
<!--TODO: think about using requirements.txt instead of pip install.-->
188
190
189
191
@@ -193,7 +195,7 @@ Were you wondering what "whitenoise" thing was? It's a tool for serve so-called
193
195
194
196
We'll find out a bit more about static files later in the tutorial, when we edit the CSS for our site.
195
197
196
-
For now we just need to run an extra command called "collectstatic", on the server. It tells Django to gather up all the static files it needs on the server. Mostly, these are the static files that make the admin site look pretty at the moment.
198
+
For now we just need to run an extra command called `collectstatic`, on the server. It tells Django to gather up all the static files it needs on the server. Mostly, these are the static files that make the admin site look pretty at the moment.
197
199
198
200
199
201
20:20 ~ $ python manage.py collectstatic
@@ -210,11 +212,11 @@ For now we just need to run an extra command called "collectstatic", on the serv
210
212
211
213
Type "yes", and away it goes! Don't you love making computers print out pages and pages of impenetrable text? I always make little noises to accompany it. Brp, brp brp...
62 static files copied to '/home/edith/my-first-blog/static'.
219
221
220
222
@@ -291,13 +293,19 @@ We're all done! Hit the big green **Reload** button and you'll be able to go vi
291
293
292
294
## Debugging tips
293
295
294
-
If you see an error when you try to visit your site, the first place to look for some debugging info is in your **error log** -- you'll find a link to this on the PythonAnywhere web tab. See if there are any error messages in there. The most recent ones are at the bottom. Common problems include
296
+
If you see an error when you try to visit your site, the first place to look for some debugging info is in your **error log** -- you'll find a link to this on the PythonAnywhere [Web tab](https://www.pythonanywhere.com/web_app_setup/). See if there are any error messages in there; the most recent ones are at the bottom. Common problems include:
297
+
298
+
- Forgetting one of the steps we did in the console: creating the virtualenv, activating it, installing Django into it, running collectstatic, migrating the database
299
+
300
+
- Making a mistake in the virtualenv path on the Web tab -- there will usually be a little red error message on there, if there is a problem
301
+
302
+
- Making a mistake in the WSGI configuration file -- did you get the path to your my-first-blog folder right?
303
+
304
+
- Did you pick the same version of Python for your virtualenv as you did for your web app? Both should be 3.4.
295
305
296
-
- forgetting one of the steps we did in the console: creating the virtualenv, activating it, installing Django into it, running collectstatic, initialising the database
297
-
- making a mistake in the virtualenv path on the web tab -- there will usually be a little red error message on there, if there is a problem
298
-
- making a mistake in the WSGI configuration file -- did you get the path to your my-first-blog folder right?
306
+
- There are some [general debugging tips on the PythonAnywhere wiki](https://www.pythonanywhere.com/wiki/DebuggingImportError)
0 commit comments