Somewhat hacky setup. Syncing the arcane compose file itself ends up with stop arcane

[stavros-k]

So, if you have arcane in a git repo and you sync it, it will do the up command and "redeploy".
Tho right after it is stopped it wont come up.

This is somewhat expected. But I was wondering if the defer of c.Close() was skipped, would this let the docker daemon actually bring arcane back up?

arcane/backend/pkg/projects/cmds.go

Line 50 in a43551e

defer func() { _ = c.Close() }()

Now, if this works, I dont suggest we do this for all stacks, maybe a label on arcane itself can be added ie (com.arcane.self=true).

[stavros-k]

Thinking it again now, it would not really work. Even if we did a fork+exec. As the container dies.

[stavros-k]

Another observation, is that once you add arcane as a project, you cannot remove it :P
(Yes, yes I know! I'm going to extra mile to try and break it LOL)

[stavros-k]

Maybe we can have an option to create a git sync job, but not create a project out of it.

That way someone can sync the arcane compose file to the host automatically, and can have a cronjob doing docker compose up -d every now and then.
So arcane won't kill it self.