1. Open the Octopus Manager and make sure the service has started, then naviate to the web portal (mine is at http://localhost/app#/)
  2. On the portal, Create your first environment and Add Environment, naming it Test, then Add Deployment Target (reading https://octopus.com/docs/infrastructure/deployment-targets)
  3. Select Windows for the type of target, then Listening Tentacle. Download the Tentacle (I chose 64 bit)
  4. Run the tentacle installer, installing in default location, and start the Tentacle Manager
  5. Select Get Started, then Listening Tentacle. I set the install location to D:\Octopus\Test-Tentacle, and the listen port as 10933, the default, adding a Windows Firewall exception, and copying the thumbprint that the Octopus portal gave me.
  6. The Hostname I entered as my PC’s IP address (run command prompt, type in ipconfig) then click next
  7. Test Tentacle as the display name, Test for the environment, a new role ‘db-server’, and all the rest as default, then save
  8. I then created another environment called Production, and went through a similar process for the Deployment target
    • Since all SQL instances are on my local machine, I think I will be using variables in the actual project to deploy to different instances
  9. I then noticed an icon saying “Upgrade available” so I clicked on that to upgrade “Calamari”, whatever that is
  10. Then to Projects, and I’ve created a new one called “SQL Octopus Deployment Demo”
  11. Define the deployment process, add step, and choose “Run a Script”
  12. Leave the defaults, choose the db-server role, select Powershell for the inline source code, and use:
    • Write-Host “Hello, World!”
  13. Create a release to test it, Deploy to Test, then Deploy to Production

Okay, well, we made some progress. I’m not sure if I’ll be able to get an actual SQL deployment working, but hopefully. Octopus is going without major errors so that’s good.