Last post Feb 08, 2017 02:27 AM by Jean Sun
Feb 07, 2017 09:53 AM|Rehaan|LINK
We have an Asp.net application that we maintain individually to customers. Means, we have deployed the application separately in all the customer servers. So whenever there is a patch, we need to go to all the customer's site or via Team-viewer to patch.
Furthermore, we have to maintain the latest code on our own server. This surely not the best way to maintain the application.
What is the best way to maintain the application like this?
What can we do to make it less hectic?
Is there any software to do the patching on remote servers?
How can we change the infrastructure of the application so that we need to maintain only one copy of the code for all the customers?
Feb 07, 2017 11:40 AM|kaushalparik27|LINK
Do you have single copy of code for all customers? Or do you have different code copies per customer? I think if you maintain versioning of database and application on each deployment, that can avoid confusion.
Also, for patch; if it involves getting Team-viewer to reach to customer's web server; at least you can automate pre-compiling of website to generate content on your end, automate (with the help of batch file or power shell script) backup old content and database
on customer's server and overwrite new content on website.
hope that helps./.
Feb 08, 2017 02:27 AM|Jean Sun|LINK
Solution One － You can use some version control tool(Git, SubVersion...)
1. First upload your website file to the Version Control Server
2. Then set your customers's website root folder to use Version Control file.
3. One you update server files, your customers can just use version control tool update feature to update their website to the least version.
Solution Two - If all your customers's website files are same, you can put your website files into one network share folder, then map customers's website root folder to this network share folder. Then you just need to update the website folder in the network
share folder. This solution may have some potential issues when you need to update the website frequently.