When to use serverSideProps - Payload Nextjs Custom Server Template?

Taun

last month

6

 export const getServerSideProps: GetServerSideProps = async (ctx) => {
  const slug = ctx.params?.slug ? (ctx.params.slug as string[]).join('/') : 'home';

  const pageQuery = await payload.find({
    collection: 'pages',
    where: {
      slug: {
        equals: slug,
      },
    },
  });

• 

  Jarrod

  Payload Team

  last month

  I think SSG is a great approach. When running Payload and NextJS on the same process, it's not really possible to use SSG. You could instead deploy your frontend to vercel as SSG and your backend on another provider like DigitalOcean or our Cloud platform.

  
  
  

  You need your db to be running before you can run

  yarn next build

  , bc when you build a project to generate the static pages it needs the db to be online to make requests in the NextJS getStatic functions and generate the static data.

  
  
  

  Using getServerSide functions allows payload and next to be run on the same process since no page builds are required.

• 

  Taun

  last month

  Thanks Jarrod. Unless the website has lots of blog posts, I should rather go SSG right? Otherwise there's going to be a lengthy initial loading time of SSG and the mobile data of the user is going to get chowed? I live in South Africa, mobile data is a luxury.

  
  

  
  

  I could use a hybrid model using Nextjs and Payload right? Eg. Landing pages are SSG and blog posts & portfolio are SSR?