feat: support running on a read-only filesystem #131
Conversation
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
paulswartz
force-pushed
the
read-only
branch
4 times, most recently
from
2811a30 to
9bd96ae
Compare
Contributor
Author
Docker containers can run on a read-only filesystem, which has some security benefits. The current updater implementation writes the .tgz file to the filesystem, so it does not work in such an environment. This provides a `read_only_fs?` configuration which stores the data in memory while loading, and does not write the ETS table to disk for future loading.
paulswartz
force-pushed
the
read-only
branch
from
9bd96ae to
29b93ba
Compare
Contributor
Author
|
Rebased on top of the latest master, and remove the other implementation of the GitHub CI. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Docker containers can run on a read-only filesystem, which has some security benefits. The current updater implementation writes the .tgz file to the filesystem, so it does not work in such an environment.
This provides a
read_only_fs?configuration which stores the data in memory while loading, and does not write the ETS table to disk for future loading.