You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 8, 2021. It is now read-only.
I don't like how Bor is managed via the provided scripts, especially started via start.sh and outputting everything to an ever-growing log file which reduces visibility. But since editing anything in the scripts will either be overwritten by a new pull or risk missing out on any updates/changes if using own scripts, there needs to be a better default way to manage Bor. I suggest using systemd or junking the scripts and leaving it up to us so we can use screen or termui as with the other three servers.
The text was updated successfully, but these errors were encountered:
Hey! We are releasing documentation regarding using systemd and docker builds today, please check those out. Other than that you can always choose to not run the script and run the commands given there manually.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I don't like how Bor is managed via the provided scripts, especially started via start.sh and outputting everything to an ever-growing log file which reduces visibility. But since editing anything in the scripts will either be overwritten by a new pull or risk missing out on any updates/changes if using own scripts, there needs to be a better default way to manage Bor. I suggest using systemd or junking the scripts and leaving it up to us so we can use screen or termui as with the other three servers.
The text was updated successfully, but these errors were encountered: