This repository for the Sitecore MVP site. It is built using Sitecore 10.2.
The Sitecore MVP site is an Open Source project and as such we welcome community contributions, though Sitecore has a "No commitment" approach to this repository. Please read the Code of Conduct and Contribution Guide before participating
- .NET Core (>= v 3.1) and .NET Framework 4.8
- Approx 40gb HD space
- Okta Developer Account
- Valid Sitecore license
-
🏃♂️ Run the Start-Environment script from an elevated PowerShell terminal
.\Start-Environment -LicensePath "C:\path\to\license.xml"
Note: The LicensePath argument only has to be used on the initial run of the script. The license file must be named
license.xml
, the script copies it to the folder.\docker\license
where it also can be placed or updated manually.You must use an elevated/Administrator PowerShell terminal
Windows Terminal looks best but the built-in Windows Powershell 5.1 terminal works too. -
☕ Follow the on screen instructions.
Note: that you will be asked to fill in the following values with your Okta developer account details:
- OKTA_DOMAIN (must include protocol, e.g.
OKTA_DOMAIN=https://dev-your-id.okta.com
) - OKTA_CLIENT_ID
- OKTA_CLIENT_SECRET
Sign up for an Okta Developer Account
If the wizard is aborted prematurely or if the container build fails then use the
-InitializeEnvFile
switch to re-run the full wizard..\Start-Environment.ps1 -InitializeEnvFile
- OKTA_DOMAIN (must include protocol, e.g.
-
🔑 When prompted, log into Sitecore via your browser, and accept the device authorization.
-
🚀 Wait for the startup script to open a browser tab with the Sitecore Launchpad.
-
🛑 To Stop the environment again
.\Stop-Environment.ps1
If you only want to start either the MVP or the SUGCON rendering container(s), you can use one of the following switch args
-StartSugconSites
-StartMvpSite
If none of these are passed to the script all rendering containers are started.
Example:
.\Start-Environment -StartSugconSites
If have issues running the site locally, please refer to the Troubleshooting page on the wiki before opening an issue.