Skip to content

v1.0.0

Choose a tag to compare

@JoshGill3882 JoshGill3882 released this 07 Sep 10:52
· 371 commits to main since this release
739124d

The first release under the Vecta name, and the first one with an audience.

A self-hosted, single-user task manager: tasks with Markdown descriptions grouped by status, flat categories with assignable colours, single-admin authentication, and one Docker image that serves either SQLite or PostgreSQL.

docker pull ghcr.io/joshgill3882/vecta:v1.0.0
sha256:1e8e6c3ed7d7f821043a36fa32b07da135ce8e84c0952bb415542d11e2f51ef6
linux/amd64 · linux/arm64

Signed with cosign, verifiable without an account:

cosign verify \
  --certificate-identity-regexp "^https://github.com/JoshGill3882/Vecta/.github/workflows/publish.yml@refs/tags/v1.0.0$" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  ghcr.io/joshgill3882/vecta:v1.0.0

Getting started

Two paths: pull the pre-built image with the compose file attached to this release, or clone and build. Either way the container applies its own migrations on start.

curl -LO https://github.com/JoshGill3882/Vecta/releases/download/v1.0.0/docker-compose.prod.yml
curl -Lo .env https://github.com/JoshGill3882/Vecta/releases/download/v1.0.0/env.example
# edit .env — set ADMIN_PASSWORD and SESSION_SECRET

docker compose -f docker-compose.prod.yml up -d

-L is required — these URLs redirect, and curl without it writes an empty file and exits successfully.

The README covers both paths for the current release.

Upgrading from v0.1.0

That release was published under the project's previous name, so this upgrade needs two one-off changes before the usual pull and up -d do anything:

  1. Replace docker-compose.prod.yml with the current one. The image moved to ghcr.io/joshgill3882/vecta. Skip this and pull re-fetches the old image and reports success.
  2. Rename TMS_VERSION to VECTA_VERSION in .env. The old name is not read, so a pinned version is silently ignored.

Keep your existing directory. Compose derives the volume name from the project name, and that from the directory — so re-cloning into Vecta/ looks for a volume that does not exist yet, creates it empty, and starts a healthy instance with none of your data in it. The old volume is untouched beside it. Full detail in the CHANGELOG.

You will also be signed out once — the session cookie was renamed.

The upgrade was verified end to end on both SQLite and PostgreSQL: the migration applies unattended on start, and a full structural comparison across the upgrade differs only by the migration row and the changed column default, with every task and category row byte-identical.

Changed since v0.1.0

  • The project is Vecta, publishing to ghcr.io/joshgill3882/vecta
  • VECTA_VERSION replaces TMS_VERSION
  • The session cookie is Vecta-Auth
  • The optional Postgres service's database is named vecta

Fixed

  • Setting PORT no longer leaves the app unreachable and the container permanently unhealthy
  • New categories get a default colour that clears AA contrast as chip text

Security

Vecta stands between the internet and your data, so please read the security section before exposing an instance: set a real ADMIN_PASSWORD, generate your own SESSION_SECRET, and terminate TLS with a reverse proxy in front of the container.

Found a vulnerability? Report it privately rather than in a public issue.

What's next

The roadmap as it stood at this release: search, filter and sort come first, then due dates. The current roadmap has moved on.