You you are right .
sarwat555
ausimian
I finally released 1.0.0 of Castle. Some decent improvements:
- Castle no longer runs via the release script. It now ships a separate
castlescript inbinthat brings the environment in correctly, and through which you can access the unpack/install/commit commands. - It does config expansion into
sys.configin a separate temporary node - It supports upgrades that require emulator restarts.
As before, it still depends on Forecastle for build time support, notably mix tasks for appup/relup generation and checking. It also provides support for testing appups and relups.
4
arcanemachine
Very nice. I can’t believe I’ve never heard of this package before! Seems like it could be very useful.
1
krasenyp
The documentation states “an external supervisor such as systemd, Docker, Kubernetes or runit for upgrades that restart the emulator” is a requirement. On FreeBSD, we use the simple daemon program for program supervision. Should I do anything specific so I can use castle in this environment where the listed supervisors don’t exist or are not used?
0
ausimian
I haven’t tested this, but it could work - something like this:
# rc.d
pidfile="/var/run/${name}.pid"
procname="/usr/sbin/daemon"
command="/usr/sbin/daemon"
command_args="-r -R 2 -P ${pidfile} -u my_app -S -T ${name} /usr/local/my_app/bin/my_app start"
-r because if a restart is required, the beam will exit 0.
If that doesn’t work, I’d be happy to take a further look, but I don’t normally run FreeBSD, so might take a day or two to confirm
0
krasenyp
Thank you! I already have supervision working but was wondering if castle does something special, like communicating with the supervisor explicitly. My impression is that it’s not, which is good for me.
1