1
How best to automate deploy ?
Having 1 deploy for each client, what is the easiest way to maintain all these deploys ? Database Migrations and all version processing?
In an example you have 100 customers
1 answer
1
A good start is in Alternative 2 of this reply, where I explain how to create transformations for the archive web.config. Here is one more example.
For your case, there would have to be a transformation per customer. The advantage of this is that not only the Connection string can be modified, but any and all client configuration.
The procedure is completely Azure-friendly as you can choose which configuration to use at the time of the Web Deploy.
Browser other questions tagged sql sql-server asp.net-mvc-5 entity-framework-6
You are not signed in. Login or sign up in order to post.
I would not open an instance per user, just for testing. I would do a single instance and it can log into it.
– Leonel Sanches da Silva
@Romaniomorrisonmendez, Doubt is related to automated deploy, and easy maintenance of 100+ deploy from the same application...
– Rod
For this case, multitenence was going to be a hand on the wheel. Just a deploy with creation of environment per user.
– Leonel Sanches da Silva
@Gypsy omorrisonmendez thought you were not in favor of the multi tenant...
– Rod
Depends on the situation. Pro case of individualization of the environment per user, I am in favor.
– Leonel Sanches da Silva
@Romaniomorrisonmendez and per company? in corporate applications?
– Rod
Then I guess I better not do multilieutenant.
– Leonel Sanches da Silva
@Ciganomorrisonmendez ah, now it made sense...is what I want to know...how to maintain version for this type of application......
– Rod
Make up your mind. It’s either for the user or for the company. There is no case that solves everything.
– Leonel Sanches da Silva
@Ciganomorrisonmendez no multi tenant, single per company only
– Rod