Add Deploy to PandaStack button#308
Conversation
|
@ajaysourcedigital is attempting to deploy a commit to the Blazity Team on Vercel. A member of the Team first needs to authorize it. |
📝 WalkthroughWalkthroughREADME documentation updated to include a "Deploy to PandaStack" button option in the "One click deploy" section, providing users with an additional one-click deployment method alongside Vercel and Netlify. ChangesDocumentation: PandaStack Deployment Button
Estimated Code Review Effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Warning |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Line 94: The deploy badge URL hardcodes incorrect PandaStack params
(type=static, buildCmd=npm+run+build, outputDir=dist); remove these query
parameters from the badge link so PandaStack can auto-detect settings instead of
forcing npm, static type, and dist output. Specifically, edit the README line
containing the deploy badge URL (the Markdown link with the deploy-button.svg)
to drop the query string parameters `type=static`, `buildCmd=npm+run+build`, and
`outputDir=dist`; leave the base deploy URL so PandaStack will detect this
repo's Yarn-based build (actual build uses yarn tinacms server:start -c "next
build") and Next.js default output (.next) and not treat it as a purely static
site.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| Clone the repository and one-click deploy to Vercel for free! | ||
|
|
||
| [](https://vercel.com/new/git/external?repository-url=https://github.com/Blazity/next-saas-starter) | ||
| [](https://dashboard.pandastack.io/deploy?repo=Blazity/next-saas-starter&type=static&buildCmd=npm+run+build&outputDir=dist) |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify whether this repo actually builds to "dist" and whether npm is the intended package manager.
set -e
echo "== package.json scripts =="
rg -n --glob '**/package.json' '"scripts"|\"build\"|\"export\"|\"start\"'
echo
echo "== Next.js config output/distDir hints =="
fd -i 'next.config.*' --exec rg -n 'output|distDir|export'
echo
echo "== References to dist output directory =="
rg -n '\bdist\b' README.mdRepository: Blazity/next-saas-starter
Length of output: 231
🏁 Script executed:
#!/bin/bash
# Verify build configuration and package manager preference for this Next.js project
echo "== package.json build-related scripts =="
cat package.json | grep -A 20 '"scripts"'
echo ""
echo "== Check for next.config files =="
fd -i 'next.config' -type f
echo ""
echo "== Check next.config content for output/distDir/export settings =="
fd -i 'next.config' -type f -exec cat {} \;
echo ""
echo "== References to 'dist' in README.md =="
grep -n 'dist' README.md || echo "(no 'dist' references found)"
echo ""
echo "== Check .gitignore for 'dist' reference =="
grep -n 'dist' .gitignore 2>/dev/null || echo "(no .gitignore or no 'dist' entry)"
echo ""
echo "== Primary package manager indicator (check for yarn.lock vs package-lock.json) =="
ls -la | grep -E 'yarn.lock|package-lock.json' || echo "(checking git history...)"
git ls-files | grep -E 'yarn.lock|package-lock.json' | head -5Repository: Blazity/next-saas-starter
Length of output: 1733
Deploy button params are incorrect and will break one-click deployment.
Line 94 hardcodes type=static, buildCmd=npm+run+build, and outputDir=dist, but all three conflict with the actual project configuration:
- The project uses yarn for all commands (see
package.jsonscripts), not npm. The build script isyarn tinacms server:start -c "next build", notnpm run build. - There is no next.config file in the repository, so Next.js uses the default output directory
.next(notdist). The only reference to "dist" in this README is the line being reviewed. - The
type=staticparameter is inappropriate for a Next.js app with TinaCMS (a headless CMS for SSR/hybrid rendering), not a static site.
Removing these hardcoded parameters and letting PandaStack auto-detect the configuration is the correct fix.
Suggested adjustment
-[](https://dashboard.pandastack.io/deploy?repo=Blazity/next-saas-starter&type=static&buildCmd=npm+run+build&outputDir=dist)
+[](https://dashboard.pandastack.io/deploy?repo=Blazity/next-saas-starter)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| [](https://dashboard.pandastack.io/deploy?repo=Blazity/next-saas-starter&type=static&buildCmd=npm+run+build&outputDir=dist) | |
| [](https://dashboard.pandastack.io/deploy?repo=Blazity/next-saas-starter) |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` at line 94, The deploy badge URL hardcodes incorrect PandaStack
params (type=static, buildCmd=npm+run+build, outputDir=dist); remove these query
parameters from the badge link so PandaStack can auto-detect settings instead of
forcing npm, static type, and dist output. Specifically, edit the README line
containing the deploy badge URL (the Markdown link with the deploy-button.svg)
to drop the query string parameters `type=static`, `buildCmd=npm+run+build`, and
`outputDir=dist`; leave the base deploy URL so PandaStack will detect this
repo's Yarn-based build (actual build uses yarn tinacms server:start -c "next
build") and Next.js default output (.next) and not treat it as a purely static
site.
1 participant
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
Happy to adjust build settings or output directory if needed. Feel free to close if you'd prefer to keep one button. 🙂
Summary by CodeRabbit