No description
  • TypeScript 61.4%
  • Svelte 31.2%
  • JavaScript 5.1%
  • CSS 1.3%
  • Dockerfile 0.5%
  • Other 0.4%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
CrazedDog df184fd719
All checks were successful
Deploy / test (push) Successful in 2m50s
Deploy / build (push) Successful in 4m42s
Deploy / deploy (push) Successful in 37s
fix: install docker CLI + git in runtime image
Stack actions (start/stop/restart/scale), compose validate and deploy all
shell out to 'docker compose'; deploy/rollback shell out to git. Neither
binary was in the image — every such call 500'd with 'spawn docker
ENOENT' (e.g. clicking stop on a stack). Both use the mounted socket /
host checkouts, so only the CLI binaries were missing.
2026-08-06 11:13:40 +01:00
.forgejo/workflows ci: pin deploy remote to Forgejo (host-2222) so deploys never pull the stale Codeberg mirror 2026-08-06 10:20:21 +01:00
.plans feat(dashboard): compact pinned cards with DnD, metrics, and health 2026-07-13 08:29:18 +01:00
.vscode first commit 2026-07-10 08:19:39 +01:00
scripts fix: seed uses pg (node-postgres) not postgres.js 2026-07-10 10:48:50 +01:00
sidecar ci: Forgejo Actions deploy pipeline (registry images + odin deploy) 2026-08-06 10:12:39 +01:00
src chore: apply code-review remediation (error boundaries, tests, internal APIs) 2026-08-06 10:12:35 +01:00
static UI Overhaul 2026-07-10 10:17:23 +01:00
tests chore: apply code-review remediation (error boundaries, tests, internal APIs) 2026-08-06 10:12:35 +01:00
.dockerignore ci: Forgejo Actions deploy pipeline (registry images + odin deploy) 2026-08-06 10:12:39 +01:00
.env.example feat: Docker registry browser + enhanced images page 2026-07-16 17:37:35 +01:00
.gitignore first commit 2026-07-10 08:19:39 +01:00
.npmrc first commit 2026-07-10 08:19:39 +01:00
.prettierrc first commit 2026-07-10 08:19:39 +01:00
alerting.todo.yaml chore: apply code-review remediation (error boundaries, tests, internal APIs) 2026-08-06 10:12:35 +01:00
code-review-report.md chore: apply code-review remediation (error boundaries, tests, internal APIs) 2026-08-06 10:12:35 +01:00
debug-api.todo.yaml debug api 2026-07-10 16:57:43 +01:00
docker-compose.dev.yml fix: remove CF-Connecting-IP header (behind Traefik, not Cloudflare) 2026-07-10 09:22:43 +01:00
docker-compose.prod.yml ci: Forgejo Actions deploy pipeline (registry images + odin deploy) 2026-08-06 10:12:39 +01:00
docker-compose.test.yml fix: remove CF-Connecting-IP header (behind Traefik, not Cloudflare) 2026-07-10 09:22:43 +01:00
Dockerfile fix: install docker CLI + git in runtime image 2026-08-06 11:13:40 +01:00
drizzle.config.ts first commit 2026-07-10 08:19:39 +01:00
monitoring-ui.todo.yaml chore: mark all monitoring-ui phases complete, clean up todo.yaml 2026-07-13 14:09:20 +01:00
package-lock.json fix: replace pragmatic-drag-and-drop with native HTML5 DnD 2026-07-13 08:46:18 +01:00
package.json fix: replace pragmatic-drag-and-drop with native HTML5 DnD 2026-07-13 08:46:18 +01:00
portainer-features.todo.yaml docs: archive previous plan, add monitoring integration research brief + plan 2026-07-10 20:55:15 +01:00
README.md first commit 2026-07-10 08:19:39 +01:00
registry-images.todo.yaml feat: Docker registry browser + enhanced images page 2026-07-16 17:37:35 +01:00
svelte.config.js fix: stale-client 429 lockout + cache HTML documents 2026-08-06 10:06:35 +01:00
tsconfig.json first commit 2026-07-10 08:19:39 +01:00
ui-cleanup.todo.yaml UI Overhaul 2026-07-10 10:17:23 +01:00
vite.config.ts fix: move svelte options out of vite config so adapter-node is detected 2026-07-10 08:52:00 +01:00
vitest.config.ts first commit 2026-07-10 08:19:39 +01:00

sv

Everything you need to build a Svelte project, powered by sv.

Creating a project

If you're seeing this, you've probably already done this step. Congrats!

# create a new project
npx sv create my-app

To recreate this project with the same configuration:

# recreate this project
npx sv@0.16.1 create --template minimal --types ts --install npm odin-ui

Developing

Once you've created a project and installed dependencies with npm install (or pnpm install or yarn), start a development server:

npm run dev

# or start the server and open the app in a new browser tab
npm run dev -- --open

Building

To create a production version of your app:

npm run build

You can preview the production build with npm run preview.

To deploy your app, you may need to install an adapter for your target environment.