Add Deploy to PandaStack button#390
Conversation
|
@ajaysourcedigital is attempting to deploy a commit to the Blazity Team on Vercel. A member of the Team first needs to authorize it. |
📝 WalkthroughWalkthroughA single line was added to README.md to include a "Deploy to PandaStack" button link in the deployment section, positioned alongside the existing Vercel deployment button. ChangesDocumentation Updates
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 64: Update the PandaStack deployment URL in README.md so the outputDir
matches Next.js's build output by changing outputDir=dist to outputDir=.next,
and resolve the static-export mismatch by either removing the type=static
parameter from the URL or enabling static export in next.config.js (add output:
'export' to the NextConfig) depending on whether you intend to perform a static
export; ensure you update the README link accordingly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| Easily deploy your Next.js app with [Vercel](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=github&utm_campaign=next-enterprise) by clicking the button below: | ||
|
|
||
| [](https://vercel.com/new/git/external?repository-url=https://github.com/Blazity/next-enterprise) | ||
| [](https://dashboard.pandastack.io/deploy?repo=Blazity/next-enterprise&type=static&buildCmd=npm+run+build&outputDir=dist) |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify Next.js build configuration for PandaStack deployment
echo "=== Checking build command in package.json ==="
if [ -f "package.json" ]; then
cat package.json | jq -r '.scripts.build // "not found"'
else
echo "package.json not found"
fi
echo -e "\n=== Checking Next.js output configuration ==="
if [ -f "next.config.js" ] || [ -f "next.config.mjs" ] || [ -f "next.config.ts" ]; then
echo "Next.js config file found:"
fd -e js -e mjs -e ts '^next\.config\.' --max-depth 1 --exec cat {}
else
echo "No next.config file found"
fi
echo -e "\n=== Checking for dist directory or custom output ==="
rg -n "distDir|output" next.config.* 2>/dev/null || echo "No custom output directory configuration found"
echo -e "\n=== Typical Next.js output directories ==="
echo "Standard build: .next/"
echo "Static export: out/ (default) or custom via next.config"
echo "Current PandaStack config: dist/"Repository: Blazity/next-enterprise
Length of output: 1048
🏁 Script executed:
#!/bin/bash
# Description: Verify PandaStack URLs are accessible
echo "=== Checking PandaStack deploy button image ==="
curl -I -s -o /dev/null -w "%{http_code}" https://dashboard.pandastack.io/deploy-button.svg
echo -e "\n=== Checking PandaStack dashboard ==="
curl -I -s -o /dev/null -w "%{http_code}" https://dashboard.pandastack.io/deployRepository: Blazity/next-enterprise
Length of output: 160
Fix incorrect output directory in PandaStack deployment URL.
The deployment URL specifies outputDir=dist, but the Next.js build is configured to output to .next/ (the default for next build). The next.config.js has no custom output directory configuration, so the dist directory will not exist after building, causing deployment to fail. Change outputDir=dist to outputDir=.next.
Additionally, the type=static parameter suggests a static export, but the project is not configured for it—there's no output: 'export' in next.config.js. Either remove type=static or add the static export configuration to next.config.js.
🤖 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 64, Update the PandaStack deployment URL in README.md so
the outputDir matches Next.js's build output by changing outputDir=dist to
outputDir=.next, and resolve the static-export mismatch by either removing the
type=static parameter from the URL or enabling static export in next.config.js
(add output: 'export' to the NextConfig) depending on whether you intend to
perform a static export; ensure you update the README link accordingly.
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