Different websites per environment scenario

Manoj_Patil · 19 June 2017 23:41

Hi Dalmiro,
We have one server in each enviromnet. However each server has multiple web sites. And each web site uses a different connection string. What is the best way to set this up in octopus.

Kindly advice.
Manoj

Kenneth_Bates · 21 June 2017 02:45

Hi Manoj,

Thanks for getting in touch! I’ve caught up with your conversation with Dalmiro, and I see you’ve created a role per website already. I’ll pick up your question from here!

Regarding using a different connection string for each website, this can be done using scoped variables. Create multiple variables with the same name, and define each value to be an individual connection string to be used for your websites, and scope them accordingly to your roles. And then when you deploy, the variable that is used will be determined by which role you’re deploying to.

I’d recommend you giving a read through our documentation on variable scoping, as I think that’ll help.
https://octopus.com/docs/deploying-applications/variables/scoping-variables

Specifically for the connection string, you’re able to define variables in your project and replace the connection string in your config file with your variable values. Scoping your variables will mean a different connection string value will be used depending on where you’re deploying. Check out our docs on this as well for more info and examples.
https://octopus.com/docs/deploying-applications/configuration-files

I hope this helps. Don’t hesitate to reach out if you have any further questions.

Best regards,

Kenny

Manoj_Patil · 21 June 2017 14:42

Thanks Ken.

Regards
Manoj

Manoj_Patil · 21 June 2017 17:02

Hi Kenneth,
How can I use an octopus variable inside the project variable? I want to do something like this. Where the file dir is based on the role.

Regards
Manoj
[cid:image001.png@01D2EA86.3C1545B0]

Manoj_Patil · 22 June 2017 13:45

Hi Kenneth,
Is there an easier way to duplicate a variable set ? We have 8 websites having slightly different variables
Manoj

Kenneth_Bates · 26 June 2017 03:59

Hi Manoj,

Thanks for following up! I’m sorry about the delay in getting back to you. It looks like you’ve gotten your syntax correct for your variable value. I tested it out with a simple PowerShell script step using write-host '#{LogPath}', and I got the correct result. Does that work for you? We also have a documentation page on troubleshooting Octopus variables which could help.
https://octopus.com/docs/how-to/debug-problems-with-octopus-variables

While there’s no built-in way to duplicate a variable set. , we have an example PowerShell script that will duplicate variables within a set into a project. It’s not exactly what you need but may provide a good starting point.

github.com

OctopusDeploy/OctopusDeploy-Api/blob/master/REST/PowerShell/Variables/MigrateVariableSetVariablesToProject.ps1

$baseUri = "http://octopus.url" # <-- Update this to the base URL to your Octopus server(i.e. not including 'app' or 'api'
$apiKey = "API-xxxxxxxxxxxxxxxxxxxxxxxxxx" # <-- Update this to your API key
$headers = @{"X-Octopus-ApiKey" = $apiKey}
$libraryVariableSetId = "LibraryVariableSets-1" # <-- Update this to the Id of your variable set
$projectName = "ProejctName" # <-- Update this to the name of your project

function Get-OctopusResource([string]$uri) {
    Write-Host "[GET]: $uri"
    return Invoke-RestMethod -Method Get -Uri "$baseUri/$uri" -Headers $headers
}

function Put-OctopusResource([string]$uri, [object]$resource) {
    Write-Host "[PUT]: $uri"
    #Write-Output $resource | ConvertTo-Json -Depth 10
    Invoke-RestMethod -Method Put -Uri "$baseUri/$uri" -Body $($resource | ConvertTo-Json -Depth 10) -Headers $headers
}

$libVarSet = Get-OctopusResource "api/libraryvariablesets/$libraryVariableSetId"
#Write-Output $libVarSet | ConvertTo-Json -Depth 10
$varSet = Get-OctopusResource "api/variables/$($libVarSet.VariableSetId)"

This file has been truncated. show original

I hope this helps! Don’t hesitate to reach out if you have any further questions!

Kenny

Manoj_Patil · 26 June 2017 18:50

Hi Kenneth,
Sorry to bother you. I see this in TeamCity Logs but I do not see the package in Octopus Server Web Library->Packages Page. However I do see it on the server file system under C:\Octopus\Packages\SQ.NextGen.Service

Kindly advice. It’s a showstopper for up now.

[09:37:40][Octopus Deploy] Running command: octo.exe push --server http://tx-buildserver.surequest.cloudstorm:8888 http://tx-buildserver.surequest.cloudstorm:8888/ --apikey SECRET --package C:\TeamCity\buildAgent\work\fe9581692fa40e03\Project\NextGen\SQ.NextGen.Service\bin\SQ.Nextgen.Service.1.0.0.10.nupkg
[09:37:40][Octopus Deploy] Pushing packages to Octopus server
[09:37:40][Octopus Deploy] Octopus Deploy Command Line Tool, version 4.15.5
[09:37:40][Octopus Deploy]
[09:37:40][Octopus Deploy] Handshaking with Octopus server: http://tx-buildserver.surequest.cloudstorm:8888 http://tx-buildserver.surequest.cloudstorm:8888/
[09:37:40][Octopus Deploy] Handshake successful. Octopus version: 3.14.1; API version: 3.0.0
[09:37:40][Octopus Deploy] Authenticated as: sqoctopus <>
[09:37:40][Octopus Deploy] Pushing package: C:\TeamCity\buildAgent\work\fe9581692fa40e03\Project\NextGen\SQ.NextGen.Service\bin\SQ.Nextgen.Service.1.0.0.10.nupkg…
[09:37:40][Octopus Deploy] Push successful
[09:37:40][Octopus Deploy] Octo.exe exit code: 0

Regards
Manoj

Manoj_Patil · 26 June 2017 20:18

It work now. My bad. Typo.

From: Manoj Patil
Sent: Monday, June 26, 2017 1:51 PM
To: ‘Kenneth Bates’ tender2+dd8974db81@tenderapp.com
Subject: RE: Different websites per environment scenario [Problems #55342]

Hi Kenneth,
Sorry to bother you. I see this in TeamCity Logs but I do not see the package in Octopus Server Web Library->Packages Page. However I do see it on the server file system under C:\Octopus\Packages\SQ.NextGen.Service

Kindly advice. It’s a showstopper for up now.

[09:37:40][Octopus Deploy] Running command: octo.exe push --server http://tx-buildserver.surequest.cloudstorm:8888 http://tx-buildserver.surequest.cloudstorm:8888/ --apikey SECRET --package C:\TeamCity\buildAgent\work\fe9581692fa40e03\Project\NextGen\SQ.NextGen.Service\bin\SQ.Nextgen.Service.1.0.0.10.nupkg
[09:37:40][Octopus Deploy] Pushing packages to Octopus server
[09:37:40][Octopus Deploy] Octopus Deploy Command Line Tool, version 4.15.5
[09:37:40][Octopus Deploy]
[09:37:40][Octopus Deploy] Handshaking with Octopus server: http://tx-buildserver.surequest.cloudstorm:8888 http://tx-buildserver.surequest.cloudstorm:8888/
[09:37:40][Octopus Deploy] Handshake successful. Octopus version: 3.14.1; API version: 3.0.0
[09:37:40][Octopus Deploy] Authenticated as: sqoctopus <>
[09:37:40][Octopus Deploy] Pushing package: C:\TeamCity\buildAgent\work\fe9581692fa40e03\Project\NextGen\SQ.NextGen.Service\bin\SQ.Nextgen.Service.1.0.0.10.nupkg…
[09:37:40][Octopus Deploy] Push successful
[09:37:40][Octopus Deploy] Octo.exe exit code: 0

Regards
Manoj

Kenneth_Bates · 27 June 2017 01:41

Hi Manoj,

Great to hear it’s working now! I see you’re working with Dalmiro on a different thread, so I’ll let you work with him on your questions over there.

Best regards,

Kenny