RFC[Ouroborus]: deploy other cotainers, allow orchestration

GeoSales-Evolution / self-deployable-docker

Docker repo capable of deploying itself... or something like that

MIT License

2 stars 2 forks source link

RFC[Ouroborus]: deploy other cotainers, allow orchestration #18

Open jeffque opened 1 year ago

jeffque commented 1 year ago

As of now, Ouroborus is capable of respawning itself (calling hestia).

We must do a way that allows Ouroborus to spawn new containers (daemon mode), so that it can create some level of orchestration.

[ ] #23
[x] #24
[x] #25
[x] #26

bin/ouroborus will contrast with ouroborus as a lib.

[ ] #19
[ ] #20
[ ] #21
[ ] #22

jeffque commented 1 year ago

Some containers depends on networks. I believe that networks could be another resource to be allocated (as are containers per #25 ).

Could differentiate containers in apps and services? Also, networks should be a thing that containers could rely on. And go live to a container would guarantee that the network is also up