I'm interested in how people are securing their LIVE environments.
The last time I worked on a very large Umbraco site, we used to remove the Umbraco and Umbraco_Client folders from the production environments, so there was no risk of 'unauthorised' access.
However, it seems that if you do this, Courier won't work!
To get around this would you recommend:
=========== super smart network =======
STAGING Master -> pushes content to Live master
LIVE Master (internal, not public)
=========== ultra big firewall ==========
LIVE Public Slave
LIVE Public Slave
LIVE Public Slave
LIVE Public Slave
Slaves, use the umbraco load balancing the detect any content changes.
So although they are missing the Umbraco folders, they still get updated.
Courier, LIVE Environment Security
Hello!
I'm interested in how people are securing their LIVE environments.
The last time I worked on a very large Umbraco site, we used to remove the Umbraco and Umbraco_Client folders from the production environments, so there was no risk of 'unauthorised' access.
However, it seems that if you do this, Courier won't work!
To get around this would you recommend:
=========== super smart network =======
STAGING Master -> pushes content to Live master
LIVE Master (internal, not public)
=========== ultra big firewall ==========
LIVE Public Slave
LIVE Public Slave
LIVE Public Slave
LIVE Public Slave
Slaves, use the umbraco load balancing the detect any content changes. So although they are missing the Umbraco folders, they still get updated.
Just incase it's useful to anyone....
Here's how I was disabling access on those LIVE nodes.
This ensures a 404 error is returned.
is working on a reply...