@@ -195,11 +195,31 @@ Heroku, make a commit (`git add -A`, `git commit -m`) and then repeat the
195195previous last step (` git push heroku master ` ).
196196
197197
198- # Heroku Tips
198+ # Troubleshooting
199+
200+ * The terminal output from launching a similar project is found here:
201+ < https://output.jsbin.com/vetomif/ >
202+
203+ * ** Disabling ` collectstatic ` :** For the purpose of launching this project, you
204+ don't need the "collect static" command.
205+ * * Error message:*
206+ - ``` You're using the staticfiles app without having set the STATIC_ROOT setting to a filesystem path. ```
207+ * * Solution:* Run the suggested command:
208+ - ` heroku config:set DISABLE_COLLECTSTATIC=1 `
209+ * * Background:*
210+ - In other circumstances, you can configure this command to do various
211+ processing to your static folder, including minifying or reducing the
212+ size of CSS files, processing images and media, and also uploading
213+ all these files to an optimized web server serivce, such as Amazon S3
214+ for speedier load times. These optimizations are nice to have, but in
215+ this case it's not necessary to use the command, which is why it's
216+ safe for us to disable it.
217+
218+ * ** Customizing name:** By default, they pick a weird, random domain name, but
219+ you can customize it later if you want to have a custom name, or even a
220+ purchased domain name.
221+
222+ * ** Making corrections:** If you want to launch code to Heroku, it must be in a
223+ brand new commit. So, whenever you want to relaunch to the world, you will
224+ need to create a new commit.
199225
200- * By default, they pick a weird, random domain name, but you can customize it
201- later if you want to have a custom name, or even a purchased domain name.
202-
203- * If you want to launch code to Heroku, it must be in a brand new commit. So,
204- whenever you want to relaunch to the world, you will need to create a new
205- commit.
0 commit comments