Repository navigation
Releases
v1.2.0
Due dates, and seeing what is late — and Vecta can now be installed to a phone's home screen.
A task can now carry a due date, with a time where the time matters. The card says when it is due, the list sorts by it, and what is overdue or due today stands out, so the list answers "what needs doing first" as well as "what is there".
docker pull ghcr.io/joshgill3882/vecta:v1.2.0
sha256:71a915b2578aa1840182ae058aed930763aa6a5b6720e2de89ec507ebf460234
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.2.0$" \
--certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
ghcr.io/joshgill3882/vecta:v1.2.0Getting started
Two paths, both in the README: pull the pre-built image with the published compose file, or clone and build. Either way the container applies its own migrations on start.
The compose file and the env template are attached to this release, so they can be fetched at the version they belong to:
curl -LO https://github.com/JoshGill3882/Vecta/releases/download/v1.2.0/docker-compose.prod.yml
curl -Lo .env https://github.com/JoshGill3882/Vecta/releases/download/v1.2.0/env.exampleUpgrading from v1.1.0
docker compose pull && docker compose up -d. No variables are renamed and no configuration changes.
This release adds a database migration, a column for the due date, which the container applies on start. Back up first: migrations are one-way, and going back to v1.1.0 after this one has run is not supported. The backup steps are in the README.
If you pinned VECTA_VERSION in .env, set it to v1.2.0 before pulling, or the pull re-fetches the version you are already on.
Added
- Due dates on tasks, with an optional time of day, set from the task form. With a mouse and keyboard, type the date —
24/9/26,24 sep,tomorrowand+3all work, read day first — or pick it from a calendar with Today, Tomorrow and +1 week shortcuts. On a touch screen, the device's own date and time pickers are used instead. A line under the field previews how the date will show on the card, and the date and its time can each be cleared - Due dates on task cards, as "Due today", "Due Thu" or "Due 4 Oct", with the full date on hover. A task with a date but no time stays due until the end of that day
- Overdue tasks stand out, in red with an alert icon and a count such as "2 days overdue", and a task due today is picked out in orange. A closed task is never shown as overdue: its date reads "Was due" instead
- Sort by due date, with the Due soonest order putting tasks with no due date last
- Filter the task list by due date, from a Due menu offering Overdue, Due today, Next 7 days and No due date. Tick several to see tasks in any of them; combined with search or a category, a task must match all of them. Closed tasks are left out of every option but No due date, and when nothing matches, the message says which filters emptied the list
- The filters in use are shown as chips above the list, each removable on its own, with Clear all to drop the search and every filter at once. On a phone the chips stay on one line that scrolls sideways
- Delete a task from the task view, through the same confirmation as the card's menu, rather than closing it and finding its card first
- Install Vecta to your phone's home screen, where it opens in its own window with no address bar, under its own icon on the app's dark background. Installing needs your instance served over HTTPS, and anything that signs you in before Vecta does, such as Cloudflare Access, has to let the manifest and icons through; the README has the details
Changed
- On a phone, the task toolbar is a single row: the search field and a filter button, which opens a sheet holding the due-date and category filters and the sort. A badge on the button counts the filters in use. From 720px wide upwards the toolbar is unchanged
- Buttons show the pointer cursor on hover, not the default arrow
- Per-commit images are tagged
main-<sha>rather thandevelop-<sha>.:latest,:unstableand the version tags are unaffected, and olderdevelop-<sha>images age out under the usual retention
Fixed
- On a narrow screen, a long category name on the Categories page pushed its task count onto two lines. The name now truncates instead, with the full name on hover
- A task the server refused to save said only "Invalid input", without saying which field was wrong. The message now appears under the field it is about, as the form's own checks do, and clears once that field is edited
- Editing a task straight after creating it created a second task with the changes, leaving the first as it was. Saving from the same window now updates the task you just created
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? SECURITY.md — please use private reporting rather than a public issue.
What's next
ROADMAP.md. Logging comes next: server errors recorded so a failure says why, and a history of what changed in your tasks and categories, tracked in the v1.3 milestone.
Full detail in the CHANGELOG.
v1.1.0
Making a longer task list usable: search, filter and sort.
Once a list runs past a screenful, "where is that task" stops being answerable by scrolling. This release makes it answerable three ways, and they compose — narrow by a query and a category at once, and the result is ordered the way you chose.
docker pull ghcr.io/joshgill3882/vecta:v1.1.0
sha256:7f8ec9625ebcf558408ea615f54b31e168e72bb06b973d2e7ee682d4ce018565
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.1.0$" \
--certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
ghcr.io/joshgill3882/vecta:v1.1.0Getting started
Two paths, both in the README: pull the pre-built image with the published compose file, or clone and build. Either way the container applies its own migrations on start.
The compose file and the env template are attached to this release, so they can be fetched at the version they belong to:
curl -LO https://github.com/JoshGill3882/Vecta/releases/download/v1.1.0/docker-compose.prod.yml
curl -Lo .env https://github.com/JoshGill3882/Vecta/releases/download/v1.1.0/env.exampleUpgrading from v1.0.0
docker compose pull && docker compose up -d. Nothing else is needed — no migration steps, no renamed variables, no configuration changes.
One visible change is expected, and it is not a fault. Folded status sections come back expanded once. Which sections are folded is now remembered in a different place — that is what stops the list flashing its default state on every load — and the old setting is not carried across. Fold them again and the choice sticks as before.
Added
- Search the task list by title and description. Matches are highlighted where they appear, and the header reports how many of your tasks matched. Press
/from anywhere on the page to jump to the field, andEscto clear it - Filter by category, choosing any number at once. Tasks with no category are reachable through an explicit Uncategorised option, so nothing hides behind a filter. Deleting a category while it is selected drops it from the filter rather than leaving you with an empty list
- Sort the list by recently updated, oldest first, or title in either direction. The choice is remembered across reloads and follows you between open tabs. Ordering applies within each status section, so the sections stay in their usual order
Changed
- A status section holding no tasks now shows only its heading and a count, instead of offering a collapse control for a section with nothing in it
- The published image no longer includes the Prisma command-line tool, which was never used at runtime
Fixed
- The "No tasks yet" message appeared below the three empty status sections rather than replacing them, so a new install looked like it had a list and a message rather than neither
- The favicon was almost entirely soft glow with nothing solid behind it, leaving it close to invisible in a light-themed tab strip
- The task list no longer flashes its default order before settling. Your sort order and folded sections are applied to the page as it arrives, rather than corrected a moment after it appears
Security
Dependency advisories reported by Dependabot are cleared, including transitive ones pinned ahead of their upstream fixes.
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? SECURITY.md — please use private reporting rather than a public issue.
What's next
ROADMAP.md. Due dates, including showing overdue tasks distinctly, come next.
Full detail in the CHANGELOG.
v1.0.0
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.0Getting 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:
- Replace
docker-compose.prod.ymlwith the current one. The image moved toghcr.io/joshgill3882/vecta. Skip this andpullre-fetches the old image and reports success. - Rename
TMS_VERSIONtoVECTA_VERSIONin.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_VERSIONreplacesTMS_VERSION- The session cookie is
Vecta-Auth - The optional Postgres service's database is named
vecta
Fixed
- Setting
PORTno 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.
v1.0.0-rc1
This is a release candidate, not a release. It exists so that v1.0.0 is not the first time the release machinery runs under the new name. :latest does not point at it and will not until a non-prerelease tag is cut.
ghcr.io/joshgill3882/vecta:v1.0.0-rc1
sha256:e1f15dd8a7532844dcfe28b7c7e25cad0eae5763b2e6d9991e24c36fe1f21d25
linux/amd64 · linux/arm64 — 136.3 MB / 137.1 MB compressed
revision 90b4bf1f3f109ec5bc58ef784a225e921b540ec0
What changed since v0.1.0
The project is now Vecta, at github.com/JoshGill3882/Vecta, publishing to ghcr.io/joshgill3882/vecta.
Four changes are visible to anyone already running v0.1.0. All are one-off consequences of the rename, and all are free to make now in a way they would not be after v1.0.0:
- The image path moved. Images published under the old path are untouched and still work; nothing new is published there.
TMS_VERSIONis nowVECTA_VERSION. The old name is not read, so a pinned version is silently ignored and you get:latest.- The session cookie is now
Vecta-Auth, which signs existing sessions out once. - The optional Postgres database is named
vectarather thantaskmanager. Existing Postgres deployments should leave their own name alone.
Upgrading from v0.1.0 needs two extra steps beyond the usual pull and up -d, because your compose file points at the old image path and your .env uses the old variable name. Without them the upgrade reports success and changes nothing. See the "Coming from v0.1.0" section of the README.
Keep your existing directory. Compose derives the volume name from the project name, and that from the directory — so re-cloning into Vecta/ starts a healthy instance with an empty database while your data sits in the old volume.
Also in this candidate
- The default category colour now clears AA contrast as chip text, with a migration in both provider histories
- Setting
PORTno longer leaves the container unreachable and permanently unhealthy - All seven phase Definitions of Done audited against the code
ROADMAP.mdsplit out of the delivery plan;PLAN.mdfrozen as the record of how v1.0.0 was built
Verification
The upgrade from v0.1.0 was re-verified against this candidate's build on both SQLite and Postgres: the migration applies unattended on start, and the full structural comparison across the upgrade differs only by the migration row and the column default, with every task and category row byte-identical.
v0.1.0
The first stable release of Task Management Solution — a self-hosted, single-admin task tracker.
This release is functionally identical to v0.1.0-rc1, which was verified against both documented deployment paths on a clean machine. It is the first release published to :latest, so a tagless docker pull now resolves to real bits.
What's in it
Tasks with Markdown descriptions, categories with assignable colours, and an open / in progress / closed workflow, behind single-admin authentication. Ships as a multi-arch Docker image that applies its own migrations on start, backed by SQLite out of the box or PostgreSQL if you point DATABASE_URL at one.
See the [0.1.0] changelog entry for the full list.
Getting started
curl -O https://raw.githubusercontent.com/J-L-Dev-Studio/Task-Management-Solution/v0.1.0/docker-compose.prod.yml
curl -o .env https://raw.githubusercontent.com/J-L-Dev-Studio/Task-Management-Solution/v0.1.0/.env.example
# edit .env — set ADMIN_PASSWORD and SESSION_SECRET (the app refuses to start
# without them), and set TMS_VERSION=v0.1.0 to pin this release instead of
# tracking :latest
docker compose -f docker-compose.prod.yml up -dThe app is then on http://localhost:3000.
Full setup, configuration reference, and backup guidance are in the README.
Image
ghcr.io/j-l-dev-studio/task-management-solution:v0.1.0
Built for linux/amd64 and linux/arm64.
Digest: sha256:547c9014efb83d07d4bb1f0c138b9cf91060b8e4475d33bf25868f772e6e5159
The image is signed with cosign using keyless OIDC. Verify the bytes independently:
cosign verify \
--certificate-identity-regexp '^https://github.com/J-L-Dev-Studio/Task-Management-Solution/' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
ghcr.io/j-l-dev-studio/task-management-solution:v0.1.0Upgrading
There is nothing to upgrade from yet — this is the first stable release. If you are running v0.1.0-rc1, the application code is unchanged, so moving across is a straight image swap. Back up your volume first regardless: migrations are one-way, and downgrading after one has run is not supported.
v0.1.0-rc1
First release candidate for v0.1.0 - the complete MVP slice, cut to verify the two self-hosting paths against a versioned artifact before v0.1.0 proper.
This is a pre-release. It does not move the :latest tag, so a tagless docker pull is unaffected. Don't point it at data you care about yet.
Running it
docker pull ghcr.io/j-l-dev-studio/task-management-solution:v0.1.0-rc1Or pin the image in docker-compose-prod.yml to v0.1.0-rc1 and follow the deployment section of the README.
Requires ADMIN_PASSWORD and a SESSION_SECRET of at least 32 characters - the app refuses to start without them. See .env.example.
What's in it
- Tasks with a title, optional Markdown description, category, and an open / in progress / closed status, grouped into collapsible sections
- Inline quick-add, plus a full create/edit modal
- Categories with assignable colours; deleting one leaves its task uncategorised rather than removing them
- Single-admin authentication with an encrypted session cookie, rate-limited login, and timing-safe password comparison
- Mobile-responsive from phone width upwards
- SQLite by default, PostgreSQL opt-in - the same image serves both, selected by the shape of
DATABASE_URL linux/amd64andlinux/arm64images, migrations applied on startGET /api/healthfor Docker healthchecks and reverse proxies
Full detail in CHANGELOG.md.
Verifying the image
Images are being signed with cosign keyless - no stored signing key, and the signature binds the bytes to this repository's publish workflow:
cosign verify \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity-regexp "^https://github.com/J-L-Dev-Studio/Task-Management-Solution/" \
ghcr.io/j-l-dev-studio/task-management-solution:v0.1.0-rc1What's being tested before v0.1.0
- Both deployment paths on a fresh machine:
- build-from-clone (
docker-compose.yml) - pre-built image (
docker-compose-prod.yml)
- build-from-clone (