So I'm looking at best practices upgrading DNN in a test/dev environment when there are active changes happening in a production context. Our ops team handles all servers and has just started naming them slightly different names in a production database environment then not changing the database name when it goes live.
For example one dnn site in a test environment has this connection string
name="SiteSqlServer" connectionString="Data Source=[Server]\PROD;Initial Catalog=clientname;User ID=dnn_client;Password=*****" providerName="System.Data.SqlClient" This is driving me (module developer, integration guy) bonkers We have a meeting to discuss naming conventions and how servers should be handled and I honestly hit a 'nice guy' wall when the issue becomes, if the updates aren't done in the production context then after all the testing is done, they have to do them again in the production context, which seems to defeat the purpose of the 'promote to production' which typically does mild changes to the production database and code is promoted to the server. This may be my cognitive disconnect from older websites to newer CMS product based site management. Just want to come up with somethnig to give them that may make sense. Because it seems that Dev/Stage/Prod isn't a thing they really want to manage
Joshua,
in short: mind the DNN Platform Suggested Upgrade Path.
Hope it helps.
Happy DNNing! Michael
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.