-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
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
nixos/forgejo: changelog and migration instructions #267248
Conversation
cc @schmittlauch as per #248310 (comment) |
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.
I haven't tried the migration steps myself so far (as I do not intend to upgrade my stable forgejo instance yet), but they look plausible to me. I added some possible improvements as comments.
As issue discussions often tend to focus more on complaining and nitpicking of negative things, I explicitly want to thank you for providing the upgrade instructions lacking in the last PR. Things are going well. 🤗
Maybe I could interest you in verifying the instructions for running the forgejo module in gitea mode, that I added? Because I don't think I've got an instance with gitea module left 🙈 |
You might be lucky, I see what me and my btrfs snapshots can do this week ;) |
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.
You can test the change by building the manual yourself:
nix-build nixos/release.nix -A manual.x86_64-linux
Co-authored-by: Emily <[email protected]>
Co-authored-by: Emily <[email protected]>
as noted <!-- To avoid merge conflicts, consider adding your item at an arbitrary place in the list instead. -->
Branch - off in 3 days, so last chance to review this ... |
I think 8 of 9 commits is a single logical change -- please squash? |
@bendlas Please don't be so much in a hurry for such changes, we can always backport them, and they are not critical for branch-off. Leave the time to review them. |
ok, sorry |
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.
I successfully tested the migration by gitea-impersonation approach, it works like a charm.
As I made the error of running gitea on mariadb and renaming databases there is kind of a pain, I unfortunately could not verify the full migration instructions.
Apart from that I discovered a typo. I can of course submit a follow-up PR for this, but preferred to keep the review feedback tied to the original PR.
database.user = "gitea"; | ||
}; | ||
|
||
users.users,gitea = { |
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.
users.users,gitea = { | |
users.users.gitea = { |
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.
Ah, I see this has already been fixed in 8c441fc.
|
||
::: {.note} | ||
Migrating is, while not strictly necessary at this point, highly recommended. | ||
Both modules and projects are likely to divide further with each release. |
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.
Both modules and projects are likely to divide further with each release. | |
Both modules and projects are likely to diverge further with each release. |
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.
please do create a new PR
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.
I just did: #270256
Description of changes
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)