[screamingninja]

Not to be sceptical, but here's my initial impression. Try the "privacy" link at the bottom of their homepage.

https://flowx.io/privacy/

> Page not found (404) > Request Method: GET > Request URL: http://flowx.io/privacy/ > Raised by: wagtail.core.views.serve

> You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page.

They tout excellent app UX but the website has a lot of rough edges visually.

Again, not discounting their work. I'm still going to install and try out, but initial impressions matter.

[duanem]

Flowx dev here. I'm not sure if the 404 page or the Debug = True is the concern?? but there are two privacy pages in the help section: https://flowx.io/help/privacy/ https://flowx.io/help/privacy-policy/

I'm not a fan of website - they have become complex. I'm currently looking into static pages as a replacement.

That said, Flowx has many moving parts: app development, data servers, data processing, support, forum, website, and others. My main focus is app development and probably the least focus is the website.

[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.