You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I could do a very simple web based management UI to view the status of deployments.
It could provide status info, with a list of last deploys for each service and a button to trigger a deployment and restart a service. It could tell you if a service or image could not be found.
It could also provide buttons for other actions like 'downloading an image of a host for backup' (useful for instances that are databases and don't use shared storage; an actual use case I have).
It could easily store the data in simple SQL lite / neDB database as the amount of data would be small.
As it's just for debugging / administration the data store could be transient (and just store the data in it's local DB) or you could give it a shared volume if you wanted that info to persist.
We could also make this how the app is configured - and have it write/ it's configuration info to a JSON file that lives on the host it's running on (with an option to view / download it for backup).
This would mean you would not have to fork the repo just to deploy an instance as the config would be outside the app.
I don't want to replicate the functionality of something like Portainer so would have authentication maybe use basic auth and environment variable or a simple .htaccess file for users.
Would love feedback on if this is - or isn't - a thing people care about, and if they do, where we should draw the line.
The text was updated successfully, but these errors were encountered:
I could do a very simple web based management UI to view the status of deployments.
It could provide status info, with a list of last deploys for each service and a button to trigger a deployment and restart a service. It could tell you if a service or image could not be found.
It could also provide buttons for other actions like 'downloading an image of a host for backup' (useful for instances that are databases and don't use shared storage; an actual use case I have).
It could easily store the data in simple SQL lite / neDB database as the amount of data would be small.
As it's just for debugging / administration the data store could be transient (and just store the data in it's local DB) or you could give it a shared volume if you wanted that info to persist.
We could also make this how the app is configured - and have it write/ it's configuration info to a JSON file that lives on the host it's running on (with an option to view / download it for backup).
This would mean you would not have to fork the repo just to deploy an instance as the config would be outside the app.
( Interested in your thoughts on this @imjosh !)
I don't want to replicate the functionality of something like Portainer so would have authentication maybe use basic auth and environment variable or a simple .htaccess file for users.
Would love feedback on if this is - or isn't - a thing people care about, and if they do, where we should draw the line.
The text was updated successfully, but these errors were encountered: