Add Deploy to PandaStack button

[ajaysourcedigital]

Add Deploy to PandaStack button

This PR adds a Deploy to PandaStack button alongside the existing Vercel button.

PandaStack is a cloud deployment platform — supports static sites, containerized apps, databases, cronjobs, and more. A great alternative hosting option for your users.

What this adds

[![Deploy to PandaStack](https://dashboard.pandastack.io/deploy-button.svg)](https://dashboard.pandastack.io/deploy?repo=arhamkhnz/next-shadcn-admin-dashboard)

Happy to adjust build settings or output directory if needed. Feel free to close if you'd prefer to keep one button. 🙂

Greptile Summary

This PR adds a one-line "Deploy to PandaStack" badge to README.md alongside the existing Vercel button. The badge URL contains build parameters that do not match the project's actual Next.js setup, which would cause the deploy flow to fail or produce a broken site for anyone who clicks it.

• type=static is specified, but this project is a Next.js SSR application with server-side redirects() configured and no output: 'export' in next.config.mjs — a static deployment cannot serve it correctly.
• outputDir=dist does not exist in this project; next build writes its output to .next, so PandaStack would look for an artifact directory that is never produced.

Confidence Score: 3/5

The change is documentation-only but the deploy URL it introduces points to a misconfigured build that would fail or produce a broken deployment for every user who clicks it.

The deploy button hard-codes type=static and outputDir=dist, neither of which matches this Next.js project. The project has server-side redirects and no static-export configuration, so anyone clicking the button would get a failed or broken deployment. The fix is confined to the URL query string in one line of README.md.

README.md — the PandaStack deploy URL needs corrected type, outputDir, and a startCmd before the button is useful.

Important Files Changed

Filename	Overview
README.md	Adds a PandaStack deploy button with incorrect build parameters — type=static and outputDir=dist do not match this Next.js SSR project's actual output configuration.

Sequence Diagram

sequenceDiagram
    actor User
    participant README as README.md
    participant PandaStack as dashboard.pandastack.io
    participant Repo as GitHub Repo

    User->>README: Clicks "Deploy to PandaStack" button
    README->>PandaStack: "GET /deploy?type=static&buildCmd=npm+run+build&outputDir=dist"
    PandaStack->>Repo: Clone repository
    PandaStack->>PandaStack: Run npm run build (outputs to .next, not dist)
    PandaStack->>PandaStack: Look for output in dist/ (does not exist)
    PandaStack-->>User: Deployment fails or serves broken site
    Note over PandaStack,User: type=static skips Node.js server needed for redirects()

Loading

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
README.md:91
The deploy URL parameters `type=static` and `outputDir=dist` are both incorrect for this project. `next.config.mjs` has no `output: 'export'` setting and defines server-side `redirects()`, so this is an SSR app — not a static site. `next build` writes to `.next`, not `dist`. Deploying with these parameters will either fail at the artifact-collection step (missing `dist/`) or produce a broken deployment that cannot serve server-side routes or redirects.

```suggestion
[![Deploy to PandaStack](https://dashboard.pandastack.io/deploy-button.svg)](https://dashboard.pandastack.io/deploy?repo=arhamkhnz/next-shadcn-admin-dashboard&type=node&buildCmd=npm+run+build&startCmd=npm+run+start&outputDir=.next)
```

_{Reviews (1): Last reviewed commit: "docs: add Deploy to PandaStack button" | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[greptile-apps]

The deploy URL parameters type=static and outputDir=dist are both incorrect for this project. next.config.mjs has no output: 'export' setting and defines server-side redirects(), so this is an SSR app — not a static site. next build writes to .next, not dist. Deploying with these parameters will either fail at the artifact-collection step (missing dist/) or produce a broken deployment that cannot serve server-side routes or redirects.

Suggested change

	[](https://dashboard.pandastack.io/deploy?repo=arhamkhnz/next-shadcn-admin-dashboard&type=static&buildCmd=npm+run+build&outputDir=dist)
	[](https://dashboard.pandastack.io/deploy?repo=arhamkhnz/next-shadcn-admin-dashboard&type=node&buildCmd=npm+run+build&startCmd=npm+run+start&outputDir=.next)

Prompt To Fix With AI

This is a comment left during a code review.
Path: README.md
Line: 91

Comment:
The deploy URL parameters `type=static` and `outputDir=dist` are both incorrect for this project. `next.config.mjs` has no `output: 'export'` setting and defines server-side `redirects()`, so this is an SSR app — not a static site. `next build` writes to `.next`, not `dist`. Deploying with these parameters will either fail at the artifact-collection step (missing `dist/`) or produce a broken deployment that cannot serve server-side routes or redirects.

```suggestion
[![Deploy to PandaStack](https://dashboard.pandastack.io/deploy-button.svg)](https://dashboard.pandastack.io/deploy?repo=arhamkhnz/next-shadcn-admin-dashboard&type=node&buildCmd=npm+run+build&startCmd=npm+run+start&outputDir=.next)
```

How can I resolve this? If you propose a fix, please make it concise.