Is there a recommended approach to split deployments, i.e. a separate deployment for Admin and API?
Approaches we've considered:
disableproperties for Admin and GraphQL (but we weren't sure how to disable the REST API...)
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
build folder, and if you place all of those files on a separate host, you can deploy them separately. Just make sure you have the proper
serverURL set, pointing at the backend API location, when you build the admin panel files.