[alecfreudenberg]

Good eye! I added this to their bugs forum.

I believe they are still a team of one, and have focused on app progress and efficiency at the expense of bugs & loose ends that would typically be handled in a larger organization with dedicated teams for that sort of thing. I bet they would

Personally I find it charming. That is until I run into a security issue.

I can't speak for Flowx though.

[duanem]

I've actually already looked into the DEBUG=True issue just now. Setting it to false causes an "Internal Server Issue".

So do I spend hours looking for a fix, look into replacing it with a static pages site (I'm thinking Hugo) or just go back to porting Flowx to Apple :-)

[clawlor]

> Never deploy a site into production with DEBUG turned on.

- https://docs.djangoproject.com/en/4.1/ref/settings/#debug

Setting DEBUG = False doesn't cause in Internal Server Issue. The issue is caused by something else, having DEBUG = True just means Django will return a detailed error page, instead of a generic 500 error page.

IIRC, DEBUG = True also used to leak memory, which doesn't matter so much for local development, where it's intended to be used.

[duanem]

I changed DEBUG = False and I get an "Internal Server Error" - you can check it now while I have a quick go at finding the cause.

I want to try static page generators (Hugo) instead since they are easier to maintain. So it's a prioritization question - do I spend time fixing this bug or spend the time on migrating.

[screamingninja]

Thank you for the prompt reply!

imho, static pages site is the best way to simplify. My personal favorite is hexo.io, but ultimately pick anything that gets the job done.