Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/michaellwest/test-sitecore-packages
Test the installation of Sitecore packages.
https://github.com/michaellwest/test-sitecore-packages
Last synced: 3 months ago
JSON representation
Test the installation of Sitecore packages.
- Host: GitHub
- URL: https://github.com/michaellwest/test-sitecore-packages
- Owner: michaellwest
- Created: 2020-05-11T21:38:12.000Z (about 4 years ago)
- Default Branch: master
- Last Pushed: 2023-01-18T21:08:31.000Z (over 1 year ago)
- Last Synced: 2024-01-25T00:15:20.968Z (5 months ago)
- Language: PowerShell
- Size: 106 KB
- Stars: 1
- Watchers: 3
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
Lists
- Awesome-Sitecore - Simplified testing of package installations - Confirms package installation by converting a package into a WDP and installing it. (Packaging)
README
# Simplified testing of Sitecore package installations
Have you ever found the setup of Sitecore module packages to be time consuming and a pain to automate? Did you know that modules can be converted from the standard module zip to a web deployment version?
The following repo provides some details about how you can get started.
## Setup
1. Clone this repo
2. From an elevated prompt run the `init.ps1` with the path to the license file. An elevated prompt is only necessary for this step.
```powershell
.\init.ps1 [-LicenseXmlPath "C:\License\license.xml"] [-HostName "dev.local"] [-SitecoreAdminPassword "Password12345"] [-SqlSaPassword "Password12345"]
```
3. Build the appropriate Docker images and then start up.
```powershell
.\up.ps1 [-IncludeSps] [-IncludeSpe] [-IncludeSxa] [-IncludePackages] [-SkipBuild] [-SkipIndexing]
```
4. Tear down and cleanup code changes when done.
```powershell
.\down.ps1 [-Cleanup]
```
### Package/Code Deployment
* Packages contained within `.\docker\build\releases` will be included in the built images.
* Packages contained within `.\docker\releases` will be deployed after the containers startup.
* Code contained within `.\deploy` will be deployed any time after containers startup. This is the best way to quickly test code changes.
## Testing
* Run the script `up.ps1`
## Demo
