Much of my work is for a corporate organisation, and there is some resistance to having the CP of a CMS externally exposed. Is it possible to run the Craft CP on one internal (not available outside the network) webserver, and the front end on a separate webserver in the external DMZ which has its access to the CP turned off? Both would talk to the same database (I can see how this could work for two full versions). This is how we run our homegrown CMS which also stores all assets (CSS, JS, templates, images and PDFs) in the database, so I know I would have to find a solution for that, but I am imaging a CDN would solve that problem. What are the technical and licensing issues that need to be addressed? I want to ditch the homegrown CMSes in use, for Craft.

It isn't just the CP that would only be available inside. I want to make all the end user form data be accessible for view and 'office use' update as well i.e. so the form submissions are managed internally only.

Also, I might want to expose separate Sections as standalone websites (these are small 6-10 page medium term sites for conferences, but sometimes have their own domain. The form submissions would be consolidated). These separate sites would all be on the same external server.


1 Answer 1


It looks like this question was resolved via some extended sleuthing in the comments above:

Overall, it looks like the answer is yes, however some part of the solution lies in settings around the server environment and routing rules outside of Craft.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.