After using SS for my private projects since almost a year, I just started migrating some of clients' services to SS.
I've just encountered a problem with setting up the following environment.
I'm thinking of keeping the main instance of the project on my own secured server and creating a copy at client's hosting server, both sharing the same DB. However, I want to mantain the site on my own server, so I'd like to completely disable the CMS functionalities in the second, copied instance for security reasons (in case client's security level is unreliable).
My first thought was to use two different DB logins, one of them only with SELECT privileges, but this way I would disable some functionalities that require writing in DB, for example the comments module.
So my question is - how to disable the CMS functionality in one instance of SS? In most cases, I can just disable access to '/admin' folder in the server's config, but sometimes I am unable to edit it. Is there any way of disabling '/admin' access in SS or - the best choice - just physically removing '/admin' functionalities from the project?
Thanks for advice.