Skip to content

[egg] Next JS#13

Open
ricardoneudorfer wants to merge 2 commits into
pterodactyl:mainfrom
ricardoneudorfer:main
Open

[egg] Next JS#13
ricardoneudorfer wants to merge 2 commits into
pterodactyl:mainfrom
ricardoneudorfer:main

Conversation

@ricardoneudorfer
Copy link
Copy Markdown

@ricardoneudorfer ricardoneudorfer commented Apr 23, 2026

Adding a new Next.js egg for Ptero-Eggs. This egg allows users to host a generic Next.js application with support for GitHub auto-pull, development and production mode, npm or yarn, configurable host and port, optional logging, and official Pterodactyl Node.js yolk images.

Checklist for all submissions

  • Have you followed the guidelines in our Contributing document?

  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?

  • Have you tested and reviewed your changes with confidence that everything works?

  • Did you branch your changes and PR from that branch and not from your master branch?

    • If not, why?:
  • You verify that the start command applied does not use a shell script

    • If some script is needed then it is part of a current yolk or a PR to add one
  • The egg was exported from the panel

New egg Submissions

  1. Does your submission pass tests (server is connectable)?
  2. Does your egg use a custom docker image?
    • Have you tried to use a generic image?
    • Did you PR the necessary changes to make it work?
  3. Have you added the egg to the main README.md and any other README files in subdirectories of the egg according to the alphabetical order?
  4. Have you added a unique README.md for the egg you are adding according to the alphabetical order?
  5. You verify that the start command applied does not use a shell script
    • If some script is needed then it is part of a current yolk or a PR to add one
  6. The egg was exported from the panel

This README provides detailed instructions on running a Next.js application on a Pterodactyl server, including features, configuration variables, and logging.
@itzzjustmateo
Copy link
Copy Markdown

itzzjustmateo commented May 3, 2026

I am a Next developer and isn't Nextjs just Node with a different start up command? (npm run build / pnpm build / bun build / yarn build)

@itzzjustmateo
Copy link
Copy Markdown

but still cool, then I won't need Vercel anymore, because I know this egg was made for Next! Maybe implement a cronjob which grabs the latest files from a given GitHub

@ricardoneudorfer
Copy link
Copy Markdown
Author

I am a Next developer and isn't Nextjs just Node with a different start up command? (npm run build / pnpm build / bun build / yarn build)

Yes, pretty much. This Pterodactyl egg is simply meant to make deploying a Next.js app easier for people who do not know how to host it on a VPS themselves and do not want to depend on Vercel.

@ricardoneudorfer
Copy link
Copy Markdown
Author

but still cool, then I won't need Vercel anymore, because I know this egg was made for Next! Maybe implement a cronjob which grabs the latest files from a given GitHub

I can look into that. For now, a server restart is all that is needed, as long as auto pull is enabled in the startup settings, since the server pulls the latest files from your GitHub repository on startup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants