Running peach-web for luandro's balena deployment #133

New Issue

2022-07-28T13:28:30Z

notplants commented

2022-07-28 13:28:30 +00:00

in order to do this, we need to get peach-web to run within a docker container that is also running go-sbot.

today, I got one version of this working, but its still a WIP.

I have learned that supervisord is not recommended to use with yunohost (https://forum.yunohost.org/t/yunohost-package-with-supervisord/20384) and that systemd is not recommended to use with docker.

In this branch I created a version of peach-web which uses a config flag "SYSTEM_MANAGER" (set to either "systemd" or "supervisord"), which makes the correct calls appropriately based on this configuration.

I've got this working except for a few things which are in systemd and seem to be missing from supervisord:

an easy way to set "start at boot" (not even really sure what this means in the context of docker... I feel like in docker the assumption should be "start at boot")
getting the memory usage of go-sbot (not yet clear to me how to do this with supervisorctl)
still need to parse uptime (this is available in supervisorctl, but I haven't parsed it yet)

alternatively, we could use initv, which might make the code simpler, since we coudl use initv on debian, in yunohost and in docker, but its a bit more unwieldy to work with than systemd or supervisord.

I'm happy that the branch I made provides a working version though that could be used.

in order to do this, we need to get peach-web to run within a docker container that is also running go-sbot. today, I got one version of this working, but its still a WIP. I have learned that supervisord is not recommended to use with yunohost (https://forum.yunohost.org/t/yunohost-package-with-supervisord/20384) and that systemd is not recommended to use with docker. In [this branch](https://git.coopcloud.tech/PeachCloud/peach-workspace/src/branch/supervisorctl) I created a version of peach-web which uses a config flag "SYSTEM_MANAGER" (set to either "systemd" or "supervisord"), which makes the correct calls appropriately based on this configuration. I've got this working except for a few things which are in systemd and seem to be missing from supervisord: - an easy way to set "start at boot" (not even really sure what this means in the context of docker... I feel like in docker the assumption should be "start at boot") - getting the memory usage of go-sbot (not yet clear to me how to do this with supervisorctl) - still need to parse uptime (this is available in supervisorctl, but I haven't parsed it yet) alternatively, we could use initv, which might make the code simpler, since we coudl use initv on debian, in yunohost and in docker, but its a bit more unwieldy to work with than systemd or supervisord. I'm happy that the branch I made provides a working version though that could be used.

supervisrod.png

33 KiB

🎉 1

notplants commented

2022-07-28 13:29:42 +00:00