Decide how mutgos should be installed/deployed in production and design and test a suitable build target.
FuzzBall installed itself in /usr/games and several other locations. I always found this awkward but perhaps it's familiar.
Another way is to make a dockerfile deployment the defacto installation style. This is fairly modern but will require some thought around how to store/backup the database - keeping it inside the container itself is too risky as those are usually assumed to be ephemeral.
One thing to be aware of here is dependencies here. mutgos uses a lot of shared libraries including the third_party software.
Decide how mutgos should be installed/deployed in production and design and test a suitable build target.
FuzzBall installed itself in /usr/games and several other locations. I always found this awkward but perhaps it's familiar.
Another way is to make a dockerfile deployment the defacto installation style. This is fairly modern but will require some thought around how to store/backup the database - keeping it inside the container itself is too risky as those are usually assumed to be ephemeral.
One thing to be aware of here is dependencies here. mutgos uses a lot of shared libraries including the third_party software.