-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
ci: Provide geonames database as GitHub release asset #10916
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Strictly speaking this won't necessarily be the same version of the data as is in our release image. If that matters to you, an alternative option is to load up that image here and copy the data out of it (not as big of an issue here as it is for the nix build, since here the image will be in a very nearby cache).
It does not quite matter if it is the same version as in the weekly container build, more that there is one fixed version per release |
I didn't realise you wanted to do this in this repo, I don't like the idea of duplicating this script over here really, we now have to maintain this in two places |
I could make it a script in the base-image repo and download that in this workflow instead |
7f8d25a
to
5d496a7
Compare
I fixed that now. The script that downloads the geodata is in this PR: immich-app/base-images#79 Note that this workflow will only work once the other PR is merged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't even right though. This is probably not what is actually included in the release.
Yea, I think I have similar feelings, if we are going to publish these in the release they should be the actual ones we bundle in the release. |
If the goal is to just have a reproducible download, they can be added to git in a separate repository outside of immich. If we're going to attach them to the release, I would recommend just adding them to the base image release itself. |
599e24b
to
02bed34
Compare
ok, now this is indeed saving the exact version that is also in the release docker container. |
02bed34
to
9c38bf8
Compare
Will take a look at this on Monday and merge it in if all looks good! 🙂 |
Is there anything still to do here for me? |
Hey, apologies for the silence on this. I'll give you as brief of an update as I can for now. Essentially there are two issues here. Basically, if we were to merge something like this, it would need to exist entirely within the base-images solution, but we are hesitant on that too right now due to the fact this may all change and potentially live in a separate repository pretty soon anyway, so don't want to add something that may immediately be changed. If that happens there will likely be automated releases for all this stuff included within that repo anyway. |
Ok, for the nix build I now used the internet archive as a stopgap solution until your new system is in place |
As discussed on Discord, this adds an archive containing the geonames database at the time of release as release asset.
This is useful for reproducible builds such as on NixOS.