-
Notifications
You must be signed in to change notification settings - Fork 37
Plugins should always run in a read-only filesystem #17
Copy link
Copy link
Open
Labels
cap:2:backend-routesPlugin or server route behaviorPlugin or server route behaviorcap:7:pipelineCapability graph registration, dispatch, claims, ownership, and compatibility shimsCapability graph registration, dispatch, claims, ownership, and compatibility shimspluginRelates to a slopsmith pluginRelates to a slopsmith plugin
Description
Activity
Metadata
Metadata
Assignees
Labels
cap:2:backend-routesPlugin or server route behaviorPlugin or server route behaviorcap:7:pipelineCapability graph registration, dispatch, claims, ownership, and compatibility shimsCapability graph registration, dispatch, claims, ownership, and compatibility shimspluginRelates to a slopsmith pluginRelates to a slopsmith plugin
I spent a lot of time making PRs to fix things that wanted to write to areas that are intended to be static and read-only in a .AppImage. People iterating on slopsmith and plugins were not aware this was a problem. To eliminate this entire class of bug, Docker instructions should mount code and static assets via a read-only volume mount so everyone sees the problem when the code is written.