Mapped drive as Octopus home directory

Legacy Execution
1

Hello,

Is there any way to use a mapped network drive as Octopus home directory, instead of a drive installed directly on the machine hosting the Octopus server?
I’m interested in having Octopus built-in repository being held in a another location another then the machine I’m installing Octopus on.

2

Hi Victor,

Thanks for getting in touch!

You can absolutely have the built in repository point to a network share, you can also do this with your artifacts and task log directories. Below are the commands that you need to run to set the directories, just replace the actual share paths as required.

Octopus.Server.exe path --artifacts \\Octoshared\OctopusData\Artifacts
Octopus.Server.exe path --taskLogs \\Octoshared\OctopusData\TaskLogs
Octopus.Server.exe path --nugetRepository \\Octoshared\OctopusData\Packages

Note: the account that your Octopus Server is running as must have read/write access to these shares.

Let me know if there is anything else that I can assist with,

Regards
Alex

3

Thanks for the quick reply, Alex.
The NuGet repo is the same as the built-in repo? Sharing the same path?

4

Hi Victor,

It is, yes. That’s a legacy name from when it was just a NuGet repository :slight_smile:

Regards
Alex

1 Like
5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.