development · docker · framework

Playing around with Sitecore 10.1.1 docker containers and my simple development framework version 3.2

Some months ago, I had a chance to play around with Sitecore 10.0.1 docker containers by updating and then deploying the Sitecore solution of my simple development framework successfully. Now I wanted to deploy the Sitecore solution of my simple development framework to Sitecore version 10.1.1 (e.g Sitecore 10.1 Update 1) docker containers as well. As a consequence, my simple Sitecore development framework version 3.2 is out.

By the way, there are some other updates:

  • upgrade to Glass.Mapper.Sc.101 latest stable version 5.8.177  (thanks my fellow Sitecore MVP Micheal Edwards)
  • sf32_1
  • upgrade to Unicorn 4.1.5 + Rainbow 2.1.4 (thanks my fellow Sitecore MVPs Mark Cassidy)
  • sf32_2

Step-by-step guide for Sitecore docker container deployment

  1. please ensure to set up your development environment by following https://doc.sitecore.com/developers/100/developer-tools/en/set-up-the-environment.html
  2. create a new folder, let’s say D:\my-simple-framework and then download + unzip my simple Sitecore development framework version 3.2
  3. to avoid any conflicts, we should ensure the following ports are not being used by another process: 443, 8079, 8081, 8984, and 14330
    • stop IIS
    • stop windows services if any
    • quit Skype for sure
  4. let’s spin up our own container-based Sitecore 10.1.1 instances:
    •  rename D:\my-simple-framework\Docker\.env.example to D:\my-simple-framework\Docker\.env
    • open Windows PowerShell (run as administrator)
    • change directory to D:\my-simple-framework\Docker
    • execute .\Init -InitEnv to initialize environment variables and then input
      • LicenseXmlPath: (Ex: “C:\license\license.xml”)
      •  AdminPassword: (Ex: “b”)
    • sf32_3
    • execute .\up to spin up a new Sitecore 10.1.1 instance
    • sf32_4
    • hopefully will see something like this after a loooooooooooog operation
    • sf32_5
  5. open a browser, navigate to https://cm.viethoang.local/, we would see the default Sitecore page with a valid SSL certificate
    • don’t forget to verify the Sitecore version 10.1.1
    • sf32_6
  6. let’s deploy the Sitecore solution
    • rename D:\my-simple-framework\cake-config.json.example to cake-config.json then update the following ones
    • WebsiteRoot to deploy folder which is mounted to docker container
    • This slideshow requires JavaScript.

    • BuildToolVersions to your MS Build version on your own machine (Ex: “VS2019”)
    • rename D:\my-simple-framework\Common.LocalSettings.config.example to Common.LocalSettings.config
    • msdf26_23
    • msdf30_13
    • open Windows PowerShell (run as administrator)
    • change directory to D:\my-simple-framework
    • execute .\build -target Deploy-Docker
    • msdf26_17
    • sf32_7
    • Note: there is a new Cake build task Publish-Library-Files in order to publish “the version” of library files which are not automatically referenced by the build system but are used by Sitecore
  7. open a browser, navigate to the following ones to access Sitecore sites with HTTPS protocol in the docker environment

Notes:

Happy Sitecore Docker and Coding!

Advertisement

3 thoughts on “Playing around with Sitecore 10.1.1 docker containers and my simple development framework version 3.2

  1. I tried with your guide but when come to .\up I got an error:

    “Waiting for CM to become available…
    Invoke-RestMethod : Unable to connect to the remote server
    At D:\my-simple-framework\Docker\up.ps1:64 char:19
    + … $status = Invoke-RestMethod “http://localhost:8079/api/http/routers …”

    Like

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.