> On Jan 27, 2026, at 21:04, Ron (Subsurface) via subsurface
> <[email protected]> wrote:
>
> On 2026-01-28 14:03, Michael Keller via subsurface wrote:
>> In terms of preventing bitrot, or rather catching it before it takes
>> hold, just having the flask app and website design in the same
>> repository isn't going to give us much - we'd also have to set up a
>> CICD task that builds and spins up a full website plus backend, and
>> then runs UI tests against it.
>
> Is flask not one of those things where doing that is basically a
> one-liner? It's not my normal dev space, but I thought all the new
> cool-kid frameworks didn't require you to have a big boy webserver
> running to be able to develop and test with them?
Flask runs its own server. Doing the API testing is straightforward.
Doing web browser testing is a bit more challenging - but I've done this
for a different project, so I know how to do that in theory. Not sure that's
necessary here (because what would break is the API), but it's doable.
But what Michael said is critical - we'd need to deal with backend.
Thankfully I implemented this so that you can create a simple git repo
to test against, you don't need the backend service. So there's no upside
to adding XML support to this.
I can look into this before we merge things.
> And I'm (ultimately) thinking of this in terms of something that I
> could spin up on one of my home servers, to give me remote access to
> the subsurface instance/data running there, not something that
> strictly requires a full multi-user cloud instance backing it.
That works with the current branch. That's how I'm doing almost all
of my development :)
> Maybe I'm off track, but that's what "also has a HTML UI" means to me
> as the 3rd option after desktop and mobile apps.
Exactly. That's how I looked at this from the start. If it's only for the cloud
storage server, that's a waste and that makes testing a major PITA
>>> So you could do things like plan a dive, then have everyone on the team
>>> review
>>> it and be able to tweak it, without everyone needing to manually enter the
>>> same
>>> data into their own devices or to crowd around a single device looking over
>>> someone's shoulder.
>> I'd guess that before we get to this point we'd probably want to add
>> support for displaying the extra information needed for technical
>> dives, like dive mode or actually used gases
>
> Yes, that was very much a moonshot thought bubble with my very best
> propeller hat on more than something we're actually one small step
> from right now. :D
And for all of these changes, I am assuming what you all are saying
"then I will submit a PR that adds that feature". I am certainly not signing
up for that.
/D
_______________________________________________
subsurface mailing list -- [email protected]
To unsubscribe send an email to [email protected]
