[mwn]

Interesting. I’ll try it out with my students. Doing HTML and CSS in a Flask app seems advanced to them. I can recommend a “deploy to PythonAnywhere” guide so users can get it online. That would require your module to be part of PythonAnywhere’s environment.

[zainhoda]

What’s your timeline? As it happens, we’re also working on a Python hosting solution with a generous free tier.

[pbronez]

Do you have any additional information to share about the hosting service? Will this be a static host, a Python-first PaaS, an education-focused REPL environment, etc?

[zainhoda]

Hey there! So it’ll be a Python-first PaaS focused on running data apps. So it’ll include storage for pickle files, a simple NoSQL database, identity aware proxy so you can configure specific routes as being authenticated, secrets manager, and the ability to run background jobs on a schedule (usually some sort of ETL process or model training).

I go back and forth on the REPL. We built a REPL but then a lot of the beta users preferred the power of GitHub Codespaces so right now I’m thinking that no, it’ll not contain the REPL.

If you have a use case, would you like to beta test the hosting?

[pbronez]

Oh, that could be fun. I’ll give it a spin.

I’m working on a something like a structured-data first wiki. Most users will be unauthenticated read-only, served well by a static site. A smaller population will submit new data and edits. Submitted data will need some processing pipelines.

I’m using Dolt/Dolthub to publish high fidelity data dumps. I’ve been leaning towards doing a static site built directly from Dolthub queries, then use an offline workflow for modifying data. However if I can bring those together easily into something more like a standard dynamic site, that would be useful.

For example, I could use your native data storage for basic user profile and authentication information, like API keys for Dolthub.

[ashishsingal]

i feel PythonAnywhere is a great concept but less great execution.