Question: Is there a recommended approach to split deployments?
2 1
Hi all,
Is there a recommended approach to split deployments, i.e. a separate deployment for Admin and API?
Approaches we've considered:
- Use the
disableproperties for Admin and GraphQL (but we weren't sure how to disable the REST API...) - Disabling top level access on internal deployment
Use case:
My team wants to externally expose the Admin panel, but keep the API internal—because our app hits a service that pulls from the CMS internally (+ Cloud CDN caching).
Yes, you can—Payload's admin UI gets built to the
buildfolder, and if you place all of those files on a separate host, you can deploy them separately. Just make sure you have the properserverURLset, pointing at the backend API location, when you build the admin panel files. 👍
Open the post
Continue the discussion in GitHub
Star
Discord
online
Can't find what you're looking for?
Get help straight from the Payload team with an Enterprise License.