Octopus stores several files that are not suitable to store in the database. These include:
- Packages used by the built-in repository. These packages can often be very large in size.
- Artifacts collected during a deployment. Teams using Octopus sometimes use this feature to collect large log files and other files from machines during a deployment.
- Task logs are text files that store all of the log output from deployments and other tasks.
- Imported zip files used by the Export/Import Projects feature.
- Archived audit logs by the Archived audit logs feature.
These files must be stored on a file system. That folder can be located directly on the Windows Server hosting Octopus Deploy, however that is not something we recommend. Especially if you want to host Octopus Deploy in a container (all the files would be destroyed when the container is destroyed).
Octopus Deploy supports network file shares, as well as many cloud providers’ storage solutions. Whichever storage solution you opt for, it must meet the following requirements:
- Support the SMB or CIFS protocols.
- Be located in the same data center as the servers/container hosts that host Octopus Deploy.
This section provides configuration walkthroughs for the popular storage options our customers use.
Help us continuously improve
Please let us know if you have any feedback about this page.
Page updated on Wednesday, May 22, 2024