chore: initial code scaffold

[hkmshb]

Description

• add code to bootstrap dev environment
• add initial code scaffold for project setup
• setup Docker Compose with database and caddy services
• setup .justfile with recipes for common reoccurring tasks to run

[Muhammad-Jay]

Hey! , I love the setup so far, everything bootstraps nicely!

I ran just start and noticed a few quick things we should probably tweak before merging:

Stuff to fix:

• Postgres volume mount: In compose.infr.yml, the mount path is currently /var/lib/postgresql. Postgress writes data to /var/lib/postgresql/data, mounting the parent dir there makes Docker create an anonymous volume there instead, 3kobo-db-data is silently unused, data is lost on down.
• Missing POSTGRES_DB: Right now, it only creates the default postgres database. We should add POSTGRES_DB: ${PGNAME:-postgres} so it picks up the right name.
• Caddy healthcheck failing: It’s looking for a ./Caddyfile in the working dir, which doesn't exist. Updating the command to ["CMD", "caddy", "validate", "--config", "/etc/caddy/Caddyfile"] should fix it.
• Compose not finding .env: Because of where it's run, Compose is looking for the .env inside the docker/ directory instead of the repo root. Passing --env-file .env to the compose commands (or baking it into the .justfile compose variable) will sort that out.
• Port typo: Looks like a small typo on the fallback value: ${CADDY_PORT:-80j} should just be 80.
• Missing packages/ dir: The Oxlint/oxfmt hooks point to ./packages/*, but that folder doesn't exist yet. This will probably break CI, so we either need to add the folder or drop the args for now.

Tiny fix:

• Platform pin: The platform: linux/amd64 hardcode on the DB forces ARM machines to emulate it unnecessarily. Might be better to just drop it.
• License mismatch:package.json says ISC, but the repo's LICENSE is Apache-2.0.

[komputarist]

@hkmshb do we want to merge and close this now or it needs some work?

[hkmshb]

@hkmshb do we want to merge and close this now or it needs some work?
@komputarist Not yet. Need to address raised concerns. I'll have this fixed and provide feedback ASAP.