@b0rk My website runs like this, kind of.
It has a bare git repository, and I use a "post-receive" hook there to re-start the services (and thus re-load the code).
So deploying new content etc is "git push" (any errors from the remote scripts are echoed to the client doing the push).
Takes a bit of setup, but IMO worth it here.
@tante@b0rk sshfs has been a bit flaky in my experience. It works to mount the first time, but fails on subsequent mounts after network disconnect. That may be me not rtfming how to actually use it right though. It's only been a few times
@penguin42@b0rk +1 to this idea. I've tried other ways but almost always regretted not having a record of changes. History-rewriting (rebase and friends) is ok in this context tho.
Add comment