[GH-ISSUE #98] non-developmnet mode? #63

New issue

Closed

opened 2026-02-25 23:41:02 +03:00 by kerem · 5 comments

kerem commented

2026-02-25 23:41:02 +03:00

Owner

Originally created by @claytondukes on GitHub (Nov 29, 2016).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/98

Hi, is there a guide for setting this up on an intranet in production mode?
I have it installed, but after setting Debug = False, it still loads using http://127.0.0.1:8080

Originally created by @claytondukes on GitHub (Nov 29, 2016). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/98 Hi, is there a guide for setting this up on an intranet in production mode? I have it installed, but after setting Debug = False, it still loads using http://127.0.0.1:8080

kerem closed this issue

2026-02-25 23:41:02 +03:00

kerem commented

2026-02-25 23:41:02 +03:00

Author

Owner

@alanivey commented on GitHub (Feb 23, 2017):

👍

When searching for Django errors with Debug=False, it's nearly all solutions with setting ALLOWED_HOSTS = [ "$HOSTNAME" ] or similar. That alone did not resolve it for me, even with an asterisk as the provided value. For my own paranoia, I have my app running with basic authentication (over TLS) on all URLs except /badge/ and /ping/, but I'd ultimately like to be able to turn debug off.

@alanivey commented on GitHub (Feb 23, 2017): :+1: When searching for Django errors with Debug=False, it's nearly all solutions with setting `ALLOWED_HOSTS = [ "$HOSTNAME" ]` or similar. That alone did not resolve it for me, even with an asterisk as the provided value. For my own paranoia, I have my app running with basic authentication (over TLS) on all URLs except /badge/ and /ping/, but I'd ultimately like to be able to turn debug off.

kerem commented

2026-02-25 23:41:02 +03:00

Author

Owner

@iphoting commented on GitHub (Feb 23, 2017):

Consider turning logging as well to obtain stacktraces of the error. One of them I noted was solved by building static assets and compressing them.

@iphoting commented on GitHub (Feb 23, 2017): Consider turning logging as well to obtain stacktraces of the error. One of them I noted was solved by building static assets and compressing them.

kerem commented

2026-02-25 23:41:02 +03:00

Author

Owner

@rawlk commented on GitHub (May 24, 2019):

Don't suppose y'all have stumbled across turning off "Debug" mode?

@rawlk commented on GitHub (May 24, 2019): Don't suppose y'all have stumbled across turning off "Debug" mode?

kerem commented

2026-02-25 23:41:02 +03:00

Author

Owner

@ttr commented on GitHub (Jul 4, 2019):

in local_settings.py
DEBUG = False
no quotes around argument, capital DEBUG.
Also IIRC site_root needs to be set.

@ttr commented on GitHub (Jul 4, 2019): in local_settings.py `DEBUG = False` no quotes around argument, capital DEBUG. Also IIRC site_root needs to be set.

kerem commented

2026-02-25 23:41:02 +03:00

Author

Owner

@cuu508 commented on GitHub (Sep 4, 2019):

I've updated README with a "Running in Production" section. It's pretty minimal and some parts likely need to be expanded on. But I also think it will be out of scope to go into full detail about configuring the web server, the task runner, the database, external monitoring etc. etc.

@cuu508 commented on GitHub (Sep 4, 2019): I've updated README with a "Running in Production" section. It's pretty minimal and some parts likely need to be expanded on. But I also think it will be out of scope to go into full detail about configuring the web server, the task runner, the database, external monitoring etc. etc.