Switch from a dynamically-derived registry/GITHUB_TOKEN login to the
same pattern already proven in the ebooks project: a fixed
git.arnef.de/arnef/nidus registry/image, docker/login-action with
REGISTRY_USERNAME/REGISTRY_PASSWORD repo secrets, docker/metadata-action
for tag/label generation (version, major.minor, latest, short SHA), and
a final buildx/system prune cleanup step. Also add a manual
workflow_dispatch trigger.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Builds linux/amd64 + linux/arm64 images via Buildx/QEMU whenever a "v*"
tag is pushed or a release is published, and pushes them (tagged with
the version and "latest") to this repository's own container registry.
Written in plain GitHub Actions syntax, which Gitea Actions runs as-is.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
BREAKING CHANGE: the users:/config-based collection setup is gone. All
user, calendar, and address-book data now lives in the SQLite DB
(internal/db) and is managed exclusively via nidusctl or the web UI.
Existing deployments must recreate their users after upgrading:
nidusctl user create <username>
nidusctl calendar create <username> <name>
nidusctl addressbook create <username> <name>
- internal/db: new users, calendars, addressbooks tables with FK cascade
delete; foreign_keys pragma enabled; internal/db/users.go implements
full CRUD + bcrypt auth (CreateUser, VerifyPassword, ListUsers,
CreateCalendar/AddressBook, etc).
- internal/config: removed Users/UserConfig entirely.
- internal/auth: Basic Auth now checks credentials via db.DB instead of
cfg.Users.
- internal/caldav, internal/carddav: ListCalendars/ListAddressBooks and
Create/Delete now backed by the DB.
- internal/web: login uses db.VerifyPassword; new resources.go adds
create/delete handlers for calendars/address books at
/web/resources/{calendar,addressbook}; dashboard gained create forms
and per-card delete buttons (templ + htmx, no hyperscript).
- tools/nidusctl: new user create/delete/list/passwd commands (masked
interactive password prompt via golang.org/x/term) plus create/delete/
list subcommands for calendar/addressbook.
- cmd/server/main.go: pre-creates on-disk collections from the DB at
startup instead of cfg.Users; warns when no users exist yet.
- Updated tests to seed data via the DB; added resources_test.go for the
new web UI handlers.
- README.md and .github/copilot-instructions.md updated to document the
new nidusctl commands and the DB-backed architecture.
Verified end-to-end against a live test server: nidusctl user/calendar/
addressbook create, DAV Basic Auth PROPFIND, web login, dashboard
rendering, and web UI create/delete of resources all confirmed working.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- web/ts/login.ts: small vanilla TS module toggling the password input's
type between 'password'/'text' via a 'Show/Hide' button, so users can
rule out typos before submitting. Compiled to web/static/login.js
(ES module) via tsc (web/tsconfig.json, new 'make web-ts'/'web-assets'
Makefile targets) and loaded via <script type="module">. Compiled JS
is committed/embedded the same way as the compiled CSS — no Node.js
needed at runtime.
- Verified end-to-end against the live proxied server
(https://local.unqr.dev/web/login): POST /web/login correctly returns
303 + Set-Cookie, and the session then authorizes GET /web/ — the
server-side login flow is confirmed working correctly.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The web UI is now mounted at /web/ (previously /ui/) — cmd/server/main.go
wraps web.Server.Handler with http.StripPrefix("/web", ...), so
internal/web's own routes stay unprefixed (/, /login, /logout,
/shares/..., /static/...) and only the outer mux adds the prefix. All
templates, redirects, and cookie paths updated accordingly. The root '/'
route reverts to the original unauthenticated welcome page (linking to
/web/), and /cal/, /card/, /files/ are unaffected.
Also gitignore the bin/ build output directory.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
New internal/web package mounted at /ui/, separate from DAV Basic Auth:
- Cookie-based sessions (opaque random tokens in a new web_sessions
SQLite table, internal/db/sessions.go), checked against the same
cfg.Users/bcrypt credentials as DAV Basic Auth.
- Dashboard listing the logged-in user's own calendars/address books,
who they're shared with, and what's shared with them.
- Share/unshare directly from the dashboard, updated in place via htmx
partial swaps (POST to create/update, DELETE to revoke). Always
verifies the resource actually belongs to the logged-in user before
granting a share.
- Templates written in templ (internal/web/templates/*.templ, generated
*_templ.go committed), styled with Tailwind CSS v4 (web/input.css,
compiled to web/static/app.css), with htmx vendored as a static file
for the dynamic bits. Both are embedded into the binary at build time
(web/staticassets.go) so the compiled server has no Node.js/web/
runtime dependency.
- Wired into cmd/server/main.go at /ui/ alongside the existing /cal/,
/card/, /files/ routes; welcome page links to it.
- Tests: internal/web/server_test.go covers login success/failure, the
login-required redirect, dashboard rendering, share/unshare including
the htmx-v2-sends-DELETE-params-as-query-string quirk, and rejecting
shares of resources the user doesn't own.
- Docs: README (new 'Web UI' section, updated sharing section, project
layout, dependencies) and copilot-instructions updated accordingly.
Makefile: new templ-generate/web-deps/web-css targets.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- tools/nidusctl: subcommands `calendar {share,unshare,shares}` and
`addressbook {share,unshare,shares}`, thin wrapper around internal/db.
Warns (non-fatal) if owner/user isn't in config.yaml.
- internal/db: add SharesOfAddressBook (owner-perspective query, mirrors
SharesOfCalendar) needed by the CLI.
- internal/db: db.Open now creates the parent data directory itself, so
the CLI works standalone without requiring the server to have run first.
- Update Makefile (build bin/nidusctl, new 'nidusctl' target), README and
copilot-instructions with usage docs.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Introduce internal/db, a small SQLite-backed store (pure-Go
modernc.org/sqlite, no CGO) at <data_dir>/nidus.db holding
calendar_shares and addressbook_shares grant tables (owner, resource
name, shared-with user, read/write permission). This is the first step
towards user management and a web UI: a real datastore that a future
admin CLI/UI can build on, instead of the static config.yaml.
Wire sharing into the CalDAV/CardDAV backends:
- ListCalendars/ListAddressBooks now also include resources shared with
the requesting user, exposed under the synthetic local name
"<owner>~<name>" in the grantee's own home-set — no separate account,
no data copying, the object still physically lives under the owner's
store.Store namespace.
- All read paths (Get/List/QueryCalendarObjects, address book
equivalents) resolve the synthetic name back to (owner, real name) and
require any share (read or write) to exist.
- All write paths (Put/Delete object, DeleteCalendar/AddressBook)
additionally require a write-permission share; read-only shares get a
403 Forbidden.
- CreateCalendar/CreateAddressBook remain scoped to the acting user's own
namespace — sharing an existing collection is done via ShareCalendar/
ShareAddressBook, not by creating one directly in someone else's name.
Add internal/db/shares_test.go (grant/lookup/update/unshare/list
semantics) and internal/{caldav,carddav}/backend_test.go (shared
calendar/address book visibility, write permission enforcement,
unauthorized access rejection). Update README (features, new "Sharing
calendars and address books" section, project layout, dependencies) and
copilot-instructions.md to document the new package and sharing model.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Root handler now only serves the welcome page for GET/HEAD; all other
methods (e.g. OPTIONS, PROPFIND) return 405 with an Allow header instead
of always returning 200, fixing client capability probes and PROPFIND
misbehavior.
- Mount /files/ properly and cache one xwebdav.Handler per authenticated
user so its LockSystem persists across requests instead of being
recreated per-request (which broke LOCK/UNLOCK).
- Remove the username segment from all DAV URLs (/cal/, /card/, /files/
are now identical for every account; the acting user is always resolved
via Basic Auth, never the path).
- Reintroduce a fixed literal "home" path segment (/cal/home/,
/card/home/) to preserve the URL segment depth that go-webdav's
caldav/carddav server relies on to classify resources (principal vs.
home-set vs. collection vs. object). Removing the username had
collapsed this depth, silently misclassifying requests and returning
empty <multistatus> responses (DAVx5 "no resources found").
- Replace the store's single global mutex with per-user sharded locks so
different users' requests no longer serialize against each other.
- Add auth.NewContext test helper, WebDAV handler tests
(per-user isolation, lock persistence across requests), and a
concurrent multi-user store test.
- Update README and copilot-instructions to document the new URL scheme
and the go-webdav path-depth classification quirk.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
arnefandCopilot