build(deploy): add Dockerfiles for docs and storybook (Dokploy)

[alexgrozav]

Description

Adds production Dockerfiles for apps/docs (Nuxt node-server) and apps/storybook (static/nginx), plus a root .dockerignore. Both images build from the monorepo root and are configured for Dokploy deployment.

• apps/docs/Dockerfile: filtered pnpm install, 4 GB prerender heap, SQLite-friendly runtime user, exposes port 3000
• apps/storybook/Dockerfile: full install + turbo build of workspace deps, nginx static serve, exposes port 80
• .dockerignore: excludes .git, node_modules, build outputs, and local tooling

Related issue

Type of change

• 🐞 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that changes existing behavior)
• 📖 Documentation
• ♻️ Refactor / internal (no functional change)
• 🔧 Build / tooling / CI

Checklist

• My commits follow Conventional Commits with a package scope (e.g. feat(theme): …)
• I ran pnpm build:nodocs && pnpm lint && pnpm typecheck && pnpm test and everything passes
• I added a changeset (pnpm changeset) for changes to publishable packages, or this change only touches docs/storybook/app/playground/tests
• I added or updated tests where relevant
• I updated documentation where relevant
• I did not edit generated files (dist/, .styleframe/)
• My PR targets main and stays focused in scope

Notes / screenshots

Dokploy configuration per app:

• docs: Build Type Dockerfile, Docker File apps/docs/Dockerfile, Docker Context Path ., container port 3000
• storybook: Build Type Dockerfile, Docker File apps/storybook/Dockerfile, Docker Context Path ., container port 80

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
storybook-styleframe-dev	Building	Preview, Comment	Jul 6, 2026 4:57am
styleframe-dev	Building	Preview, Comment	Jul 6, 2026 4:57am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 57c5840

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!