Besides the system drive on my Octopus system, I have added an additional drive in which I want to use for all Octopus related data. I don’t want to store any Azure or NuGet packages on the system drive to avoid filling up the system disk.
I have all the different storage locations defined to point this particular drive but I still get NuGet packages stored on C:\Octopus\Applications.Tentacle\Packages and then those get extracted to c:\Octopus\Applications<environment><app><build version> when a NuGet package is selected for deployment. I essentially have two copies of a deployed version on the system disk. Seeing that I have all the different storage locations (tentacle, web service, and storage) pointing to the non-system drive, this sounds like a potential bug.
Am I missing something in configuration somewhere that would keep these packages from ending up on C:? I could use a link as a work-around but would prefer not to.
Thanks for getting in touch! Under Tentacle there is a configuration option for the appdir.
``
c:\Program Files\Octopus Deploy\Tentacle>tentacle.exe service --stop
c:\Program Files\Octopus Deploy\Tentacle>tentacle.exe configure --appdir "myappdir"
c:\Program Files\Octopus Deploy\Tentacle>tentacle.exe service --start
The above will change where the packages get extracted to. It controls this part of the path for both `C:\Octopus\Applications`.
Hope that helps!
Vanessa
Thanks, this appears to have done the trick - at least on the first test. One thing to note, you must do this per tentacle. I no longer have a default tentacle so it was throwing an error complaining about that.