exoframe
exoframe copied to clipboard
Exoframe is a self-hosted tool that allows simple one-command deployments using Docker
This is an issue to track overall progress on v7.0 rewrite. Plan is to rewrite / update code to use latest libs (not just versions) and ES modules (ES modules...
Currently, exoframe will build and deploy new container and remove the old one only after new one is up and running. This works fine for majority of services, but some...
Currently, exoframe-server only allows using `volume` type volumes [1]. There needs to be a way to specify other types (e.g. users might want to use `bind` type with docker socket...
In case you go with typescript. I can can continue on this just for practice my self.
Currently if project doesn't have exoframe.json for whatever reason - exoframe-server will just throw a non-descriptive error (see #312). This needs to be handled correctly.
If exoframe-server is deployed via `https`, you can still access it using `http`. But apparently it causes some weird issues (see #312). It should be possible to address this either...
Hey there, would be nice if the config file could be moved to not clutter the home directory i.e. use the Linux standard of `.config/exoframe`
Github actions are releasing soon-ish. Having a prepared github action for exoframe would be neat. The easiest way to go about it would be to fork [heroku](https://github.com/actions/heroku) (see also [npm](https://github.com/actions/npm),...
There's currently a few typical use cases for exoframe - would be great to have those as step-by-step guides in docs. Cases (to be extended): - [ ] Basic project...
See this PR / comment for more info: https://github.com/exoframejs/exoframe-server/pull/31#issuecomment-704666649