Skip to content
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

Ready for Prime Time? #3

Open
zacksiri opened this issue May 18, 2018 · 5 comments
Open

Ready for Prime Time? #3

zacksiri opened this issue May 18, 2018 · 5 comments

Comments

@zacksiri
Copy link

I've been hosting all my stuff on Alpine and was wondering if something like this existed.

After some googling I found this, and it made me super happy. Do you think this is ready for prime time? I'm also happy to start testing the package. How can I help?

@jirutka
Copy link
Owner

jirutka commented Jun 20, 2018

I don’t consider it ready yet.

  • packages_blacklistis currently hack-ish and a bit flawed (see [apk-autoupdate.in:75-98](https://github.com/jirutka/apk-autoupdate/blob/7ec9519818a122fabc2f629a796f6ec7a35a17b1/src/apk-autoupdate.in#L75-L98)). I’m waiting for support ofapk upgrade --exclude` in apk-tools (issue #8792).
  • Parameters services_blacklist and services_whitelist are currently quite confusing, I need to redesign them somehow.

Except these two issues it should be solid.

@zacksiri
Copy link
Author

zacksiri commented Jun 21, 2018

I'm abit unsure about the necessity of services_blacklist and services_whitelist I think apk-tools already handles something like this in the post-upgrade script.

If the services should be restarted post-upgrade they should be encouraged to use that hook no? And if it's a sensitive service that need to stay up then, well, they don't need to included the post-upgrade script or write a script that allow the service to be restarted without interruption (like hot code reloading)

seems like it should not be the responsibility of apk-autoupdate but the responsibility of the packages themselves.

@ernierasta
Copy link

Ahoj Kubo!
As this topic is few years old, how you see status now? There is apk upgrade --ignore if it changes anything.
You probably run apk-autoupdate in production, how do you feel about having updates automated generally?

@martin-braun
Copy link

martin-braun commented Mar 5, 2023

I know it's been years @zacksiri, but I had the same thought processing at first, but ...

No, it is not the responsibility of the package to restart its installed service, because it doesn't know about openrc. apk-autoupdate most likely calls rc-service $SERVICENAME restart.

Unlike Debian, Alpine doesn't offer a security-upgrade repository. So, apk-autoupdate can never mimic unattended-upgrades, for instance to only install security patches. However, while Debian has only major version branches, Alpine has many minor version branches that will allow you to stay on recent versions with security patches only.

apk-autoupdate should be sufficient if you stay on a "sec fixes" support level branch.

@fossdd
Copy link
Contributor

fossdd commented May 21, 2024

Is there something new? The last commit is 3 years ago and before that 6 years ago. IMO, it would be awesome to have that included in the 3.20 Alpine release instead of waiting for the last issues to be fixed (which nobody picked up in the last 6 years).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants