Dotnet core features top 10

Octopus permissions can be configured in several different ways. There are user roles, service accounts and teams. Users use AD credentials to access Octopus. are API-only accounts that should be used for automated services that integrate with Octopus Deploy

Octopus permissions can be configured in several different ways. There are user roles, service accounts and teams. Users use AD credentials to access Octopus. are API-only accounts that should be used for automated services that integrate with Octopus Deploy, and can only authenticate with an A team is a group of users, and being a member of a team gives those users certain roles, which can be scoped. Team members can be granted many different roles like "Project Viewer", "Project Deployer", etc. After a Team is created users are given access mainly via AD groups. Users outside of the Americas domain are added through a scheduled script ran by TeamCity to synchronize the different domains within our organization since Octopus can't communicate across domains.

Dotnet core features

We're still working on a better solution. the issue of running out of disk space isn't resolved entirely. Migrate current Octopus instance to a high Availability setup. This is already in progress. DB is set up, 2 Octopus nodes are installed, NAS storage share is ready. Just waiting on IT to provide the load balancing configuration. The taskLogs, artifacts and packages have been moved to the NAS share which did free up some of the storage space on the Octopus server. The main thing that is causing the disk usage to grow is the server's package cache files. These files are stored on the local Octopus server and get created when Octopus accesses a nuget from one of it's configured nuget feeds.

We're still working on a better solution. the issue of running out of disk space isn't resolved entirely. Migrate current Octopus instance to a high Availability setup. This is already in progress. DB is set up, 2 Octopus nodes are installed, NAS storage share is ready. Just waiting on IT to provide the load balancing configuration. The taskLogs, artifacts and packages have been moved to the NAS share which did free up some of the storage space on the Octopus server. The main thing that is causing the disk usage to grow is the server's package cache files. These files are stored on the local Octopus server and get created when Octopus accesses a nuget from one of it's configured nuget feeds.

Step By Step process on new technologies