feat: local backend #20
Open
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
Using sqlite to save checkpoints failed at runtime because: * Internal Mutex was a nil pointer * The help messages explaining how to create the sqlite3 database had the wrong CREATE statement * The implementation of the `LockBackend` interface had the `Fetch` function return a wrong object (a `dynamoCheckpoint` instead of a `sqliteCheckpoint`) Signed-off-by: Flavio Castelli <[email protected]>
Prior to this commit, sunlight required access to a S3-compatible server to send backend data. Now there's the possibility to store this data on the local filesystem. This is not meant to be used in production, but it hugely simplifies testing and local development. Signed-off-by: Flavio Castelli <[email protected]>
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.
I really love how easy it is to sunlight for testing/playing purposes. I've noticed however that sunlight requires access to a S3-compatible server to store the logs data. I've added the possibility to the local filesystem instead of relying on a S3 bucket.
This is not meant to be used in production, it just simplifies the setup for testing purposes.
I hope you like this change. Thanks again for the great tool!
Just for reference, this is the configuration file I used to spin up a local testing instance: