openfire: init at 4.9.0 #360
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Asked the Openfire developers about this on discourse and apparently there are a few more directories that need to be writeable in |
|
Openfire now works through an This is a good step in getting the server to run, but it's unclear to me how to update the program state on package updates in a non-destructive manner. |
eljamm
force-pushed
the
openfire
branch
4 times, most recently
from
0451e09
to
6ffb9af
Compare
|
The program's state can now be automatically migrated on package updates, following the steps in Openfire: Upgrade Guide. |
Co-authored-by: Valentin Gagarin <valentin@gagarin.work>
wegank
approved these changes
Oct 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial work for packaging Openfire. The derivation builds successfully, but the program does not work correctly, yet.
One of the issues at hand is that a writeable directory relative to
OPENFIRE_HOMEis required for logs, but the package's home directory resides in the nix store, so patching might be required to make it look elsewhere for the logs.Closes #341