{"items":[{"id":"545ff07f-92d0-4108-8534-2eda2c07833e","type":"push","org":"zhengqunkoo","repo":"docker-taskd","title":"Ignore local docker-compose.yml and add a template so sensitive Taskd configuration stays out of version control.","summary":"This change stops committed Docker Compose files from leaking environment-specific or sensitive values by adding docker-compose.yml to .gitignore and renaming the tracked file to docker-compose.yml.template. Developers still get a complete starting point for local setup, but are expected to copy and customize it outside the repo. The practical effect is safer local configuration with less risk of accidentally committing secrets.","url":"https://nomit.dev/zhengqunkoo/docker-taskd/status/d1c694dbbdcbd75d2e17e2c9928d54018a75349086d3b299e300d6492289e54c","author":"","contributors":[],"updated_at":"2021-03-21T08:05:23+00:00"},{"id":"a0832048-2e89-47cf-ae3a-ecefea7fae46","type":"push","org":"zhengqunkoo","repo":"docker-taskd","title":"Automate organization and user creation in the Docker entrypoint setup for taskd","summary":"The Docker entrypoint script has been updated to automatically create a default organization and user during the initial `taskd` server setup. It leverages new `TASKORG` and `TASKUSER` environment variables in `docker-compose.yml` to drive this process. It also automatically generates client certificates for this new user, dropping them straight into the `/var/taskd/pki/` directory. This streamlines the container's first-time setup, ensuring the server spins up immediately ready to accept authenticated client connections.","url":"https://nomit.dev/zhengqunkoo/docker-taskd/status/6bb900cdb48e434ba6e6d0f768ec38ed3e3208437721e184205deafce8c813c7","author":"","contributors":[],"updated_at":"2020-06-09T02:08:04+00:00"},{"id":"e01ea58a-4065-4243-a4ee-1bc6b93ba07c","type":"push","org":"zhengqunkoo","repo":"docker-taskd","title":"Updated Docker Compose to build the taskd service from the local Dockerfile instead of pulling a prebuilt image.","summary":"This change switches the `taskd` service in `docker-compose.yml` from using `x4121/taskd:latest` to building directly from the repository’s local `docker` context, and explicitly names the container. That makes the setup easier to customize, test, and keep in sync with local Dockerfile changes without relying on an external image being updated first. The practical effect is a more reproducible and developer-friendly local container workflow.","url":"https://nomit.dev/zhengqunkoo/docker-taskd/status/376cc963f9a0eb895c5b71560d6d634f7f2b1a6ec62c745dae6d009228836831","author":"","contributors":[],"updated_at":"2020-06-09T02:06:48+00:00"},{"id":"08ad1ed9-9e97-4fa9-9041-6003d2e08769","type":"push","org":"zhengqunkoo","repo":"docker-taskd","title":"Switch to named Docker volumes for taskd persistence","summary":"Updated the `docker-compose.yml` configuration to use a managed named volume (`taskd-data`) for persisting taskd data, replacing the previous local directory bind mount. Along with explicit service definitions, this change aligns the deployment with Docker best practices. It makes data persistence, management, and backups more robust while helping avoid common local file permission issues.","url":"https://nomit.dev/zhengqunkoo/docker-taskd/status/0556891a472e5664148db7467cb3d387d5b3a8ef9be089b7cf1aa8fef5362693","author":"","contributors":[],"updated_at":"2020-06-09T01:46:27+00:00"},{"id":"57c1dd25-5c94-4d0a-a353-db0d8b46149c","type":"push","org":"zhengqunkoo","repo":"docker-taskd","title":"Updated the Docker image to use a newer Alpine base and gosu release, while hardening the entrypoint script for safer container startup.","summary":"This change modernizes the container image by moving from Alpine 3.3 to the rolling Alpine 3 tag and upgrading gosu from 1.7 to 1.11, including a more current signature verification flow with hkps and explicit binary validation. It also cleans up the entrypoint script by consistently quoting paths and tightening the root-check conditional, which reduces the chance of shell breakage when paths or environment values are unexpected. The practical effect is a more reliable and maintainable Docker setup with safer privilege dropping at runtime.","url":"https://nomit.dev/zhengqunkoo/docker-taskd/status/998b5c2eb61c3ff6ed09495e3de81c748d4e0410f3e4dfa5eb1841fec6b15416","author":"x4121","contributors":["x4121"],"updated_at":"2019-11-27T09:13:03+00:00"}],"pagination":{"offset":0,"limit":5,"has_more":true}}