More in this section
Forums / Bugs & Issues / app_data/Sitefinity/Configuration - design change

app_data/Sitefinity/Configuration - design change

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
1 posts, 0 answered
  1. Adam
    Adam avatar
    23 posts
    Registered:
    05 Apr 2013
    07 Sep 2016
    Link to this post

    Are there any plans in the future to tame the beast that is the configuration files stored under app_data/Sitefinity/Configuration?

    It doesn't make sense to me why so much data is stored in these configs. To me, only environment-specific variables, like those found in DataConfig.config or SiteSync.config should be stored there. Everything else, such as Dynamic Modules or custom fields on existing modules is really content and content structure, and should be stored in the DB. In addition, this data should sync with the new site sync feature. 

    Having to keep these files in sync between developers, dev ops teams and site sync is a massive burden!!

    Also, given the current state of config management, why hasn't there been any documentation written on how to handle working with these configs between different teams and deployment environments? 

1 posts, 0 answered