separate nextjs + payload apps, or use the custom nextjs server?

sibergenomelast year

2

• 

  derosullast year

  Hey, I don't think any of the options you mentioned are wrong. If you're not too sure that you want to use NextJS, you probably want to keep it separate for now. The beautiful thing about Payload is that the CMS you create are mostly config files in Typescript and payload takes care of the rest. Meaning it's pretty easy to switch between the setups.

  
  
  

  One of the main advantages for the NextJS setup for both the custom server and the NextJS integration they released recently, is that you can deploy your CMS and your frontend together.

  
  
  

  So my recommendation would be, start of with the standard payload setup, try to do some things with NextJS and once you decided that you want to use NextJS. Migrate you payload collections and configs to a NextJS custom server / next-payload project.

  
  
  

  And fyi: there is a difference between nextjs-customer-server and next-payload.

  
  
  

  NextJS custom server is a combination where you run an express server and NextJS app simultaneously.

  
  

  The next-payload is a setup where you can deploy Payload "serverlessly" on for example Vercel (which is pretty awesome) directly from your NextJS project.
• 

  sibergenomelast year

  I'm pretty set on Nextjs just because of how well it pairs with payload, and since I'm familiar with react. But I agree that since payload is mostly just config then migrating the project to the nextjs custom server shouldn't be too tricky! So then I think I'll probably keep it separate projects until I feel more comfortable with nextjs and migrate if it seems beneficial, or otherwise use next-payload.

  
  

  Thanks for the help!