arnefandCopilot
7d4f28de3c
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>
32 lines
888 B
YAML
32 lines
888 B
YAML
server:
|
|
host: "0.0.0.0"
|
|
port: 8080
|
|
# Set this to your public-facing URL so discovery responses are correct.
|
|
# base_url: "https://dav.example.com"
|
|
|
|
auth:
|
|
realm: "My DAV Server"
|
|
|
|
storage:
|
|
data_dir: "./data"
|
|
|
|
logging:
|
|
level: "debug" # debug | info | warn | error
|
|
format: "text" # text | json
|
|
|
|
tls:
|
|
enabled: false
|
|
# cert_file: "/etc/ssl/certs/dav.crt"
|
|
# key_file: "/etc/ssl/private/dav.key"
|
|
|
|
# Users, calendars, and address books are no longer configured here — they
|
|
# are stored in the database (<data_dir>/nidus.db) and managed with
|
|
# nidusctl or the web UI (/web/):
|
|
#
|
|
# nidusctl user create alice --password mysecretpassword --display-name "Alice Smith" --email alice@example.com
|
|
# nidusctl calendar create alice personal
|
|
# nidusctl calendar create alice work
|
|
# nidusctl addressbook create alice contacts
|
|
#
|
|
# Run `nidusctl help` for the full command list.
|