-
-
Notifications
You must be signed in to change notification settings - Fork 418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some build and package improvements #45
Conversation
… the welcome message
e77d038 makes the installation a lot less verbose but still get the output of the ssh command (which would be supressed when -q would be used)
|
@spali dont have time to test this atm, would love to merge it. Do you have nay more test evidence or are you confident it works. Also, can you add support for cron files and bump the version to 1.1.0 |
Currently have not more evidence, I'm confident it works, but maybe someone else has time to prove that just to be sure. |
I first thought about using systemd in a container that manages all the custom services or scripts. But you will anyway have to use the ssh_proxy to start everything one level heigher. |
just made a issue to discuss the "service management" topic independent from this. |
c52809a
to
7df47b8
Compare
Have done some build and package improvements.
Hope you like it.
Tested it as you did with Ubuntu 20 with WSL2.
Last commit includes even support for building in docker or podman.
I had in mind to potentially in the future build on the UDM itself which in theory could already work with these changes... but not tested yet.
Let me know if I should change something you not agree, of if a specific change need's more explanation.
i.e. the version number of the package... removed the "-1" behind, because this package is a native debian package, which means has it's own sources included.
Next plan is to support the external disk in the UDMP #43 .
I also play with the idea to use systemd in a "controller"-container and only start this container with this package.
This would allow to not only use scripts that get started, we could put systemd service files inside boot.d or similar to have the full control an flexibility of a systemd service like schedule, logs etc. For each container or just for simple scripts, including dependencies etc.
But not a systemd expert yet... so needs some research first.