How to handle staging app ?

[fathom dock]

Hi, i'm currently on the process of migrating our site from Storipress to Payload, and with Storipress I had two instance of the same product: one on production with the SP server linked to the main branch of the github repo, and second for staging and development on Vercel linked to the dev branch.

This allowed me to work on the project on the dev branch and then once it's ready for production, I had to clone the dev branch then merge it with main to push the changes on production.

Is there a better way of doing it with Payload or should I keep working like this ? Thanks

[toxic bloom]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Email Functionality - Use SMTP
• Production Deployment - Security - The Secret Key
• Preventing Production API Abuse - Introduction
• REST API - Custom Endpoints
• Adding your own Queries and Mutations - Best practices

[fathom dock]

I was wondering if with the standard plan I can do the same but avoid Vercel? I don't see anywhere how many project you can use with each plan

[unborn ice]

Hey @fathom dock,

So recently I started using Coolify with Payload for my personal projects - you should definitely check it out as it may make your life a little easier.

Aside from that, you should continue doing what you've been doing because a) you already have a process for it, and b) it isn't really unique to Payload. I have a similar flow for my environments.

[fathom dock]

thanks, i'll take a look at Coolify.
In the meantime do you know how many projects I can have with the standard plan ?

[unborn ice]

No unfortunately as I self host, that may be a question for the Payload team