Have never tried it mightself but it is definitely possible. You would take a similar setup when you have a load balanced environment and only one of the servers holds the admin section, the other servers only have the frontend then. Since all the servers connect to the same database (or better data source as it might be in a cloud or something as well) you don't have much of an issue there. However the physical files will require a proper solution. E.g. if a user uploads an image to the media library it will by default be place into the /media/[fileUpload-property-id]/ folder of the admin website, then link to the file is stored in the database pointing to the relative path. When the frontend now tries to access the file it won't find it in its own media folder. Same applies to xslt, css, js, etc files you create in the backend.
One way to solve this is by synchronizing files between the two installations. Another way is to have one shared folder for these files where both frontend and backend get access too.
IMHO if you don't have a or multiple very good reasons to separate the two there isn't really any need to do that, it will just create a you additional headache and the benefit is negligible. Of course something like a very very tight security policy or the need to use multiple servers might make this step necessary.
this should be possible to set up on the web server, e.g. in IIS7 by using request filtering. I'm sure there are other ways as well. One thing you can't do though is use UrlRedirection to take care of this as the backend is exempt from any rewrite rules you might put in there.
Take Umbraco outside the domain
Is it possible to take Umbraco Admin section outside the website.
I want to saperate the admin section (/umbraco) on other domain / website.
Is it possible ? or is it a good practice ?
Thanks
Hi Kurniawan,
Have never tried it mightself but it is definitely possible. You would take a similar setup when you have a load balanced environment and only one of the servers holds the admin section, the other servers only have the frontend then. Since all the servers connect to the same database (or better data source as it might be in a cloud or something as well) you don't have much of an issue there. However the physical files will require a proper solution. E.g. if a user uploads an image to the media library it will by default be place into the /media/[fileUpload-property-id]/ folder of the admin website, then link to the file is stored in the database pointing to the relative path. When the frontend now tries to access the file it won't find it in its own media folder. Same applies to xslt, css, js, etc files you create in the backend.
One way to solve this is by synchronizing files between the two installations. Another way is to have one shared folder for these files where both frontend and backend get access too.
IMHO if you don't have a or multiple very good reasons to separate the two there isn't really any need to do that, it will just create a you additional headache and the benefit is negligible. Of course something like a very very tight security policy or the need to use multiple servers might make this step necessary.
Cheers,
Sascha
Hi Sascha,
Thanks.. for your reply.. It seems possible but to much risk in synchornising the file.
Do you know how if the single installation.. to protect the umbraco admin section so it can load on other domain...
but still into single installation...
so now www.company.com can't see the umbraco....admin login, etc..
but umbraco.company.com.. will have the admin section...
Can we put it into single installation but only different domain ?
Thanks
Hi Kurniawan,
this should be possible to set up on the web server, e.g. in IIS7 by using request filtering. I'm sure there are other ways as well. One thing you can't do though is use UrlRedirection to take care of this as the backend is exempt from any rewrite rules you might put in there.
Cheers,
Sascha
is working on a reply...