Those are populated via javascript, but it does occur to me that as we're templating anyway we could generate full responses server-side so that there's no hard dependency on javascript.
Either way, though, the idea is that index.html will be a base template and then different paths will just change the body content
Leaving aside the fact that it's basically a wireframe, this is pretty much as done as it's likely to get for a bit - I had been planning to do a video walkthrough of it this evening, but something's come up, so it'll have to be another day.
But, the portal can now
For superuser: List customers (including how many apps they're running)
List apps available for install (trying to avoid using the word deploy to avoid confusion with Deployment...)
Install an app and provide the generated credentials/url/etc
Activity
10-Nov-24 16:44
assigned to @btasker
10-Nov-24 17:47
mentioned in commit ff05eed1b55f170c25f93d1201b5242cfc782755
Commit: ff05eed1b55f170c25f93d1201b5242cfc782755 Author: B Tasker Date: 2024-11-10T17:46:35.000+00:00Message
feat: start to stand up a management portal (misc/pod-as-a-service#6)
10-Nov-24 17:49
It's not pretty but
Those are populated via javascript, but it does occur to me that as we're templating anyway we could generate full responses server-side so that there's no hard dependency on javascript.
Either way, though, the idea is that
index.htmlwill be a base template and then different paths will just change the body content12-Nov-24 19:42
mentioned in commit 0b8ef7394008b3fb792a5734a6f152a41f89e82e
Commit: 0b8ef7394008b3fb792a5734a6f152a41f89e82e Author: B Tasker Date: 2024-11-12T19:42:12.000+00:00Message
feat: implement ability to deploy apps via webportal (misc/pod-as-a-service#6)
19-Nov-24 18:03
Leaving aside the fact that it's basically a wireframe, this is pretty much as done as it's likely to get for a bit - I had been planning to do a video walkthrough of it this evening, but something's come up, so it'll have to be another day.
But, the portal can now
Deployment...)