-
Notifications
You must be signed in to change notification settings - Fork 59
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
Add support for sqlite/postgres database backends #96
Conversation
735c78d
to
82ca797
Compare
@guggero: review reminder |
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.
Nice work! Happy to see we could re-use so much existing code. Main comments are related to some schema modifications to simplify some of the biz logic, and make unique fields explicit.
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.
Looks great, thanks a lot!
Found a couple of smaller things, but those should be relatively easy to address.
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.
Look preeetty good, ran things locally and found an issue with the sqlite
file config if one isn't explicitly specified. I think we want to allow people to just say db_backend: sqlite
and not have to explicitly set where the file should go (actually use the default).
6192579
to
4f26827
Compare
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.
tACK, LGTM 🎉
Tested in the Pool server integration test.
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.
LGTM 🛺
Needs a rebase! |
This PR adds sqlite/postgres support for aperture.
Currently the server uses a couple of interfaces
SecretStore
andOnionStore
that are implemented in this PR. To keep consistency with other code bases aperture uses the same toolssqlc
/goang-migrate
and the same interfaces than Taproot AssetsFixes #95