Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Feature BranchesFeature Branches
Previous
 
Next
New Post
3/29/2017 5:16 PM
 

I am using DNN 7 for a company website with a SQL Server back-end.  I have a few workarounds in place in terms of Feature Branching.  This a common practice of separating code changes (features) off of the main branch so the team of developers can also access our dev branch and publish/execute other changes.  However with each feature branch we take we have to or are going through an entire setup of DNN for each feature.  Is there a way to cut a feature branch and run it on the same instance of the initial install?  Also is there a way to share this branch?  Each developer has a local install, so the database currently is relevant only to the machine it's on. We use separate environments for production, dev, and testing.  I have workarounds in place just curious as to what everyone else is doing..

 
New Post
3/30/2017 3:14 PM
 

Branching, for us, is a last resort. We utilize extensions and providers to override or change core functionality. What sort of workarounds are you creating?


Rich Campbell
Engage : Your ideas, Our know-how
DNN Experts
St. Louis, MO
314.966.4000
 
New Post
3/30/2017 3:30 PM
 

Well we have a couple workarounds really nothing to efficient hence asking the question to see what others in the community are doing.  The main issue is sharing the database, as this is the main feature to running DNN.  Everything lives in the database, creating a feature branch is just code.  So pointing the code to a shareable database is target.

  1. We are using a DNN server installation and having all developers use this database as their development database.  So we share common DNN features.  Then create feature branches, so the code is featured specific while using a shared resource.  Not a bad thing, but if something in DNN changes (not frequently) we just need to communicate it.  
  2. We tried using several installations of DNN Databases, one for each developer, one for each branch, and it was a pain because we had to do installation and replenish licenses for each.  And again not quite as dynamic as we liked.
  3. Originally we were trying shelve sets (TFS)/stashes (GIT) of code.  With local DNN Database installs, merging the stashes on top of local environment.  Worked but highly inefficient.

The shared DNN database seems to be working just curious as to what others do.  We, also tried using Evotiva for database backups to share.  This helped as well as sharing the resource but again everything requires reinstalling/licensing.  The challenge is surrounds itself around the database. 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Feature BranchesFeature Branches


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out