Skip to content

sync dev with latest Rc/0.2.0 hotfixes#897

Open
nachog00 wants to merge 10 commits intodevfrom
rc/0.2.0
Open

sync dev with latest Rc/0.2.0 hotfixes#897
nachog00 wants to merge 10 commits intodevfrom
rc/0.2.0

Conversation

@nachog00
Copy link
Contributor

@nachog00 nachog00 commented Mar 2, 2026

No description provided.

zancas and others added 9 commits February 24, 2026 08:29
The CLI now requires a subcommand (e.g. `zainod start`). This change:

- Adds entrypoint.sh that creates writable directories with correct
  ownership before dropping privileges to the non-root user
- Uses ENTRYPOINT for the script and CMD for the default subcommand
- Follows zebra's pattern for handling volume mount permissions
- Adds XDG_RUNTIME_DIR support to the xdg module for cookie paths
- Refactors default_ephemeral_cookie_path() to use the xdg module

Docker usage:
- `docker run zaino` → runs `zainod start`
- `docker run zaino --help` → shows help
- `docker run zaino generate-config` → generates config

Note: Custom paths set via TOML config file require the user to ensure
those directories exist with appropriate permissions.
- Entrypoint now skips chown on read-only mounts instead of failing
- Added test_environment/test-docker-permissions.sh for local testing
Create symlinks in the container so Docker users can mount to simple
paths (/app/config, /app/data) while zaino continues using XDG defaults
internally:
  - /app/config -> ~/.config/zaino
  - /app/data -> ~/.cache/zaino

Updated entrypoint to handle /app/* paths directly and updated test
script and documentation to use the new paths.

Fixes: #876
fix(docker): use ENTRYPOINT/CMD split with privilege dropping
Move entrypoint script from /usr/local/bin/entrypoint.sh to /entrypoint.sh
following the common Docker convention used by official images (postgres,
nginx, redis). This makes it clear the script is container infrastructure,
not an application binary.

Fixes #879
fix: version bump, startup logging, and entrypoint location
@nachog00
Copy link
Contributor Author

nachog00 commented Mar 2, 2026

there's a problem with this flow i just realised about. pushing the Update Branch button forcibly merged dev into the rc branch... that means, applying hotfixes onto the rc branch to allow dev to keep accepting non rc changes is limited, cause the moment we want to update dev with the latest fixes, we then need to dump ALL of dev into the rc...

Hotfix: sync bugs and unecessary lints
@idky137
Copy link
Contributor

idky137 commented Mar 3, 2026

there's a problem with this flow i just realised about. pushing the Update Branch button forcibly merged dev into the rc branch... that means, applying hotfixes onto the rc branch to allow dev to keep accepting non rc changes is limited, cause the moment we want to update dev with the latest fixes, we then need to dump ALL of dev into the rc...

Ye this is why I push for having a more straightforward freeze on dev while we are in the release process as it gets complicated trying to maintain multiple branches and often extra things get added that were not meant to be (and may not be as tested as we would like for a stable release). It is also easy for subtle bug fixes to get lost when dealing with conflicts between the two branches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants