Octopus Set Up and Configuration on Windows 10


Octopus Deploy is an automated deployment and release management server. It is designed to simplify deployment of ASP.NET applications, Windows Services and databases.
First you need to download octopus on your local system or cloud from below URL.
https://octopus.com/trial







Download for 64 or 32 bit as per your available system.






After downloading the trail version you just create the trial key with filling few basic information on same browser.










































Now you will get trial key on your email and in next window as well. To start installation on your local system just click on msi file downloaded from octopus site.






After installing the octopus you just start octopus and enter required information in first screen to validate the license key. After this step give path for deployment packages and other settings.






























In next screen select service account so here I am selecting local user system account for my requirement.






Time to fill data base connection information. You need to fill data base server name and credentials as well. Other than credentials it requires to select database where you want to save octopus related information.




Set the virtual directory name for octopus deploy server.



Set the Authentication to interact with users on octopus server.




























After filling all information regarding authenticate user on octopus deployment server click on install button to complete the installation on your system.



Once installation is completed then you will see octopus browser which have information for web portal, storage etc.



Basic setup of octopus is done. Let’s start work on deployment of your project. In my next article I will try to deploy dot net core project using octopus.


Happy Learning!!!



Comments

Post a Comment

Popular posts from this blog

Error : DependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.adobe.aem:uber-jar:jar:apis -> version 6.3.0 vs 6.4.0

Image
I got above error after adding dependency in Maven POM xml file placed under newly created AEM arch type and running command  mvn -PautoInstallPackage clean install . Error : DependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.adobe.aem:uber-jar:jar:apis -> version 6.3.0 vs 6.4.0 After google and gone through few article I got command ( mvn -PautoInstallPackage -Padobe-public clean install) . Once I run this command this issue with jar compatibility was resolved. Happy Learning!!!
Read more

ERROR Exception while handling event Sitecore.Eventing.Remote.PublishEndRemoteEventException: System.AggregateExceptionMessage: One or more exceptions occurred while processing the subscribers to the 'publish:end:remote'

I was getting below error while working with cache management on CM and CD server. Actually my code was working fine on CM server but I was not able to access or clear cache object on CD server because of wrong event selection.  PID[18108] Error       ManagedPoolThread #3 16:24:16 ERROR Exception while handling event Sitecore.Eventing.Remote.PublishEndRemoteEventException: System.AggregateExceptionMessage: One or more exceptions occurred while processing the subscribers to the 'publish:end:remote' event.Source: Sitecore.Kernelat Sitecore.Events.Event.EventSubscribers.RaiseEvent(String eventName, Object[] parameters, EventResult result)at Sitecore.Events.Event.RaiseEvent(String eventName, Object[] parameters)at Sitecore.Eventing.Subscription`1.Invoke(Object instance, EventContext context)at Sitecore.Eventing.EventProvider.RaiseEvent(Object event, Type eventType, EventContext context) Above error comes due to wrong event args access in CD server. T...
Read more

Error : Sorry, there was an error : unauthorized_client in Sitecore 9.1 login

Image
After adding a new binding from IIS on my sitecore 9.1 instance I was getting unauthorized client error while login with newly added binding URL. To fix this issue I added AllowedCorsOriginsGroup in xml file placed at File Name :  Sitecore.IdentityServer.Host.xml Location : C:\inetpub\wwwroot\9Dot1.identityserver\Config\production After adding field tag AllowedCorsOriginsGroup in  Sitecore.IdentityServer.Host.xml file I was able to login properly with newly added URL. Also you can fix this issue by placing a pipe operator beside of old AllowedCorsOriginsGroup as below. <AllowedCorsOriginsGroup1>http://9Dot1.sc | http://jss.9Dot1.sc</AllowedCorsOriginsGroup1 Happy Learning!!!
Read more