sneak/pixa
1
0
Fork 0
Code Issues 51 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

µPaaS deployment setup #17

New Issue
Open
opened 2026-03-02 08:47:37 +01:00 by clawbot · 3 comments
clawbot commented 2026-03-02 08:47:37 +01:00
Collaborator
Copy Link

Goal

Set up pixa for deployment via µPaaS on fsn1app1 (paas.datavi.be).

Tasks

  • Create prod branch from main
  • Verify Dockerfile builds and runs correctly in production mode
  • Configure µPaaS app definition (service name, port, env vars, volumes)
  • Create initial main → prod PR for first deployment
  • Verify deployment is healthy

Notes

Deploy pattern: PRs target main, periodic main → prod PRs for deployment. µPaaS auto-deploys from prod branch.

Pre-requisite: pixa must reach 1.0 feature completeness before deployment.

## Goal Set up pixa for deployment via [µPaaS](https://git.eeqj.de/sneak/upaas) on `fsn1app1` (paas.datavi.be). ## Tasks - [ ] Create `prod` branch from `main` - [ ] Verify Dockerfile builds and runs correctly in production mode - [ ] Configure µPaaS app definition (service name, port, env vars, volumes) - [ ] Create initial `main` → `prod` PR for first deployment - [ ] Verify deployment is healthy ## Notes Deploy pattern: PRs target `main`, periodic `main` → `prod` PRs for deployment. µPaaS auto-deploys from `prod` branch. Pre-requisite: pixa must reach 1.0 feature completeness before deployment.
sneak was assigned by clawbot 2026-03-02 08:47:37 +01:00
sneak reopened this issue 2026-03-04 12:11:28 +01:00
sneak commented 2026-03-04 12:12:07 +01:00
Owner
Copy Link

‘main’ will be the prod branch

‘main’ will be the prod branch
sneak was unassigned by clawbot 2026-03-15 22:09:27 +01:00
clawbot self-assigned this 2026-03-15 22:09:27 +01:00
clawbot removed their assignment 2026-03-18 03:21:29 +01:00
sneak was assigned by clawbot 2026-03-18 03:21:29 +01:00
sneak was unassigned by clawbot 2026-07-25 12:10:11 +02:00
clawbot commented 2026-08-07 18:06:58 +02:00
Author
Collaborator
Copy Link

Status checkpoint (session handoff): still gated on 1.0 feature completeness, per the issue body. Where that stands as of main at 6573b9d:

  • make check is now fully green on main under the current linter (#47/#48 merged); the manual auth/encrypted-URL test pass is done and awaiting review as PR #50.
  • Remaining P0s before 1.0: cache size management/eviction (#51) and startup config validation (#52), in that order per TODO.md; P1/P2 backlog also lives in TODO.md.
  • Reminder for whoever executes this issue later: per sneak's comment above, main will be the prod branch — the "create prod branch" / "main → prod PR" tasks in the issue body are superseded.
Status checkpoint (session handoff): still gated on 1.0 feature completeness, per the issue body. Where that stands as of `main` at `6573b9d`: - `make check` is now fully green on `main` under the current linter (#47/#48 merged); the manual auth/encrypted-URL test pass is done and awaiting review as PR #50. - Remaining P0s before 1.0: cache size management/eviction (#51) and startup config validation (#52), in that order per `TODO.md`; P1/P2 backlog also lives in `TODO.md`. - Reminder for whoever executes this issue later: per sneak's comment above, `main` will be the prod branch — the "create `prod` branch" / "`main` → `prod` PR" tasks in the issue body are superseded.
clawbot commented 2026-08-09 03:38:02 +02:00
Author
Collaborator
Copy Link

Manager note: opened a 1.0.0 milestone to track the remaining pre-release work units. Deliberately leaving this issue out of it, because this issue's own Notes state the prerequisite plainly: "pixa must reach 1.0 feature completeness before deployment." Deployment is the step that follows the milestone, not part of it.

Will revisit once 1.0.0 closes out.

Manager note: opened a `1.0.0` milestone to track the remaining pre-release work units. Deliberately leaving this issue **out** of it, because this issue's own Notes state the prerequisite plainly: "pixa must reach 1.0 feature completeness before deployment." Deployment is the step that follows the milestone, not part of it. Will revisit once `1.0.0` closes out.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
merge-ready
needs-checks
needs-rebase
needs-review
needs-rework
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
clawbot sneak
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/pixa#17
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?