: How to Get all the settings/permissions/etc. required for a web site/application? I have no access to the production server. I need to get all the configurations made to a web site that got
I have no access to the production server. I need to get all the configurations made to a web site that got it working in the first place.
The developers who did the deployment are now happy somewhere else, and I can only ask the IT department to get me information from server, they wont let me to browse it myself.
My question is how can I get all the settings/configurations required on that IIS server and permissions required for the directories under that site? Is there a tool I can tell the IT Department to use to get all non default specifics of website/web app/directory permissions etc. set up on the production server? Just getting a copy of directory wont tell me anything about the permissions and other specifics required to have the new updated site running in that environment.
Is there a smart way to approach this problem? The only thing I can think of is to get a fresh server and try to get the site running there documenting all the steps. Then handing the image and steps to IT people and hoping that what worked in one environment is going to work on a different environment! A bit of hit and miss really.
There are number of other sensitive applications/web sites/services running on that production server that there is no way I can get an image of the server for my trial and error experiments.
More posts by @Vandalay111
1 Comments
Sorted by latest first Latest Oldest Best
I will be addressing this:
Is there a smart way to approach this problem? The only thing I can
think of is to get a fresh server and try to get the site running
there documenting all the steps. Then handing the image and steps to
IT people and hoping that what worked in one environment is going to
work on a different environment!
Having managed large-scale production environments and development environments, I will give you the following advice.
The only thing I can think of is to get a fresh server and try to get
the site running there documenting all the steps.
You should have a working copy of the system within the development environment so that you are intimately aware of what needs to happen from the development perspective. Detail the snot out of this! Make sure every tiny detail is documented as you go along. It will pay dividends!!
Then handing the image and steps to IT people and hoping that what
worked in one environment is going to work on a different environment!
Absolutely not! You want a build for your work and not the entire server. You are not the expert and cannot mitigate security and operational issues. You do want to create build instructions and supply installs and other build material, but only for what you are introducing into the environment and not server level stuff. The reason for this is simple. If you supply it, you are responsible for it. Any production environment should never allow development to dictate the OS and supply an image. In fact, most will not even let you supply the application installs and will prefer to check this out for themselves to ensure that the latest and safest version of any application is installed. In some environments, some applications are not allowed at all and that should be taken into account as well. It all depends on how tightly controlled and well managed your production environment is.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.