This is needed because Dockerfile cannot be used to to run sqlite, since the Dockerfile provides no pre-made directory for storing the database (which means mounted volumes have incorrect permissions since the container runs as a non-root user). Dockerfile.prod fixes this by storing all files (keys and the DB) in /data.
The default Dockerfile is apparently just used for development. The upstream plans to publish an image using Dockerfile.prod: https://github.com/writefreely/writefreely/pull/1136
This is needed because Dockerfile cannot be used to to run sqlite, since the Dockerfile provides no pre-made directory for storing the database (which means mounted volumes have incorrect permissions since the container runs as a non-root user). Dockerfile.prod fixes this by storing all files (keys and the DB) in `/data`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The default Dockerfile is apparently just used for development. The upstream plans to publish an image using Dockerfile.prod: https://github.com/writefreely/writefreely/pull/1136
This is needed because Dockerfile cannot be used to to run sqlite, since the Dockerfile provides no pre-made directory for storing the database (which means mounted volumes have incorrect permissions since the container runs as a non-root user). Dockerfile.prod fixes this by storing all files (keys and the DB) in
/data.