This PR makes the recipe use sqlite by default, since I'm pretty sure it's not possible to disable services that exist in the default compose.yml file. Plus, I think sqlite will be a better default experience and use fewer resources.
Fixed the config version env vars not matching the config names
Moved the config to /usr/share/writefreely, because I can't put the config in the data storage dir. This forces us to use the "-c" flag every time we run the binary (really wish the upstream would let us set the config file path with an env var)
Explicitly set the paths to the templates, keys, etc., since we have to use non-default locations for all of them due to volume mounting issues.
This PR makes the recipe use sqlite by default, since I'm pretty sure it's not possible to disable services that exist in the default compose.yml file. Plus, I think sqlite will be a better default experience and use fewer resources.
Other changes:
- Added several more config options
- Removed the post-install step, that was fixed in v0.14: https://github.com/writefreely/writefreely/pull/618
- Updated to 0.16.0 (https://git.coopcloud.tech/coop-cloud-chaos-patchs/docker-writefreely/pulls/1 )
- Fixed the image name
- Since the image name was broken, this confirms there are no current users, so we don't have to worry about backward-compatibility
- Added entrypoint to run key generation, database initialization, and migrations
- Moved all data to `/data` (required https://git.coopcloud.tech/coop-cloud-chaos-patchs/docker-writefreely/pulls/2)
- Fixed the config version env vars not matching the config names
- Moved the config to /usr/share/writefreely, because I can't put the config in the data storage dir. This forces us to use the "-c" flag every time we run the binary (really wish the upstream would let us set the config file path with an env var)
- Explicitly set the paths to the templates, keys, etc., since we have to use non-default locations for all of them due to volume mounting issues.
Closes #1
Ahh well I can confirm this recipe has zero current users 😅
```
$ docker pull git.coopcloud.tech/coop-cloud-chaos-patchs/writefreely:v0.15.1
Error response from daemon: manifest unknown
```
So no need to worry about testing migrations haha
I think this PR is ready now, but I'd want to do another quick round of testing after merging https://git.coopcloud.tech/coop-cloud-chaos-patchs/docker-writefreely/pulls/2
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.
This PR makes the recipe use sqlite by default, since I'm pretty sure it's not possible to disable services that exist in the default compose.yml file. Plus, I think sqlite will be a better default experience and use fewer resources.
Other changes:
/data(required coop-cloud-chaos-patchs/docker-writefreely#2)Closes #1
Need to test
LGTM, nice one! A great update 🎉
Long live sqlite 🫡
1e39d1d6c1to8e51569ee4Ahh well I can confirm this recipe has zero current users 😅
So no need to worry about testing migrations haha
I think this PR is ready now, but I'd want to do another quick round of testing after merging coop-cloud-chaos-patchs/docker-writefreely#2
8153d2e557tocff1b66703Well it was kind of a nightmare but it's working now!
fe384d2ddbto8f0dc48169The beauty of our project: only one must suffer 😂
Thank you!