To my understanding, running a traditional server-side web app is at odds with the original principle of tilde—it’s not just another server, it’s a server bound by the creative constraint of an architecture that serves only static pages to the public internet. There are still lots of ways to make your page dynamic, like building your app all on the front end, or adding a cronjob that updates or generates pages on a schedule rather than in response to a request. What’s the goal of your flask app, Leo?
~brendn
On Oct 28, 2020, at 1:30 AM, xwindows xwindows@tilde.club wrote:
On Wed, 28 Oct 2020, leo wrote:
I can even run the app on the Flask-built-in server and the app says that it "is running on http://127.0.0.1:8050/?, but obviously I cannot make tilde.club's whole underlying web server make listen on port 8050!
User processes can open a [random wild port] to listen, yes; but such port cannot be connected from outside- only from inside the club. Accessing such port from outside would simply result in connect timeout.
So, I am curious how I could run that flask webapp, so that it can be accessed from the outside through a subpath of my homepage www.tilde.club/~halloleo/, for example http://www.tilde.club/~halloleo/flask.
As far as I know, the club is not configured to allow this. For an authoritative answer, wait for ~ben's and/or ~deepend's reply.
Regards, ~xwindows