Solution Level Config Files

paul_dambra · 8 November 2016 10:08

We’re using Octopus 2.4.7.85

I have a solution with projects in a structure like:

I’d like to have Octopus config files inside both the service and web project for config they don’t share

classLibraryA
classLibraryB
windowsService
- Octopus\
  - windowsService.dev.config
  - windowsService.staging.config
aspNetMVCWebProject
- Octopus\
  - web.dev.config
  - web.staging.config

But also have solution level files for shared config (i.e. they both reference the same SQL server)

Octopus\
- shared.dev.config
- shared.staging.config
classLibraryA
classLibraryB
windowsService
- Octopus\
  - windowsService.dev.config
  - windowsService.staging.config
aspNetMVCWebProject
- Octopus\
  - web.dev.config
  - web.staging.config

Is that possible?

robpearson · 10 November 2016 10:45

Hi Paul,

Thanks for getting in touch. I’m not sure if I totally understand your question but I’ll talk about a couple common scenarios.

If you’re asking if it’s possible to package a project with that structure? i.e. Using OctoPack? Yes, it should be possible but you would need to create a custom .nuspec file to include the parent files and use Octopack or nuget.exe.
The following pages have more information on this starting with Octopack.
If the configuration files are config transforms and you’re asking if we can apply them in different locations, the answer is yes. We should be able to apply them assuming they’re included in your app/service package as mentioned above. Our confirmation transforms page provides a bit more information on this. http://docs.octopusdeploy.com/display/OD/Configuration+files#Configurationfiles-ConfigurationTransformationConfigurationtransforms

If this doesn’t answer your question, can you tell me a bit more about what you’re trying to achieve?

Let me know how you go!

Thanks

Rob