Conversation
Collaborator
|
holding off on merging pending written modules for supported database engines, either here in community-modules or in upstream edit: man i'm behind, i didn't realize postgres was merged upstream recently. guess it's just pending on MySQL at this point |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 commit for the ForgeJo and Gitea. The services use shared logic from modules/lib/mkGitForge.nix to avoid repeating same thing over and over since they work in same way. I tested both on my finix configuration and didn't experience any issues yet. Currently supports only sqlite3 since PostgreSQL and MySQL don't have service files.