Content
@
0 reply
0 recast
0 reaction
matt ðŸ’
@matthewmorek
OpenNext exists because no one at CloudFlare or SST seem to understand (or want to acknowledge), that Next.js deployed outside of Vercel is a dynamic Node.js app and not a static site with interactive bits. Naturally, you can't just upload it to an S3 bucket and call it a day. Maybe they should just switch to Astro?
5 replies
1 recast
27 reactions
Arti Villa
@artivilla.eth
what about deploying to railway.app ? same issues? I had so many issues with Astro. sparse docs, no community. have things changed?
1 reply
0 recast
0 reaction
matt ðŸ’
@matthewmorek
Haven’t tried Next.js on Railway, though it would not be much different to deploying it on a VPS like Digital Ocean, etc. As for Astro, there are tons of docs and the community is way bigger than it used to be, so you might be in luck. However, I wouldn’t treat Astro like a full stack framework: it’s not.
1 reply
0 recast
0 reaction
Arti Villa
@artivilla.eth
i’m using railway for servers. what are the concerns beyond that? i think my site has very little static data so im not sure what is the real value here.
1 reply
0 recast
0 reaction
matt ðŸ’
@matthewmorek
i don't think you should have any concerns when self-hostign on Railway, though because of the way deploying works (using nixpacks), you may need a bit of a custom configuration. check details here: https://nextjs.org/docs/app/building-your-application/deploying#self-hosting
1 reply
0 recast
0 reaction
Arti Villa
@artivilla.eth
yeah there are peeps in the community who are super helpful. not concerned at all but curious who here as used it and if not, outside vercel what have they tried?
0 reply
0 recast
1 reaction
