Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI testing #41

Closed
wants to merge 87 commits into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
87 commits
Select commit Hold shift + click to select a range
18beb26
Rename solution
Piedone Dec 26, 2022
53fd653
Updating all packages
Piedone Dec 26, 2022
4d62542
Adding Letters from Fiume theme with recipe
Piedone Dec 26, 2022
34e6c7b
Fixing base theme
Piedone Dec 26, 2022
75204c7
Adding Google Analytics tag
Piedone Dec 26, 2022
9e66d0a
Adding favicon
Piedone Dec 26, 2022
727e228
Updating recipe
Piedone Dec 26, 2022
863a3be
Proper license, Readme
Piedone Dec 27, 2022
9ebc79b
Recipe update
Piedone Dec 27, 2022
c79bde2
And now without Layers export
Piedone Dec 27, 2022
2d8db48
Adding CSS for links in content <li>s
Piedone Dec 27, 2022
3928c2c
Relative virtual paths for icons
Piedone Dec 27, 2022
7239368
Adapting deployment script to optional --clear
Piedone Dec 27, 2022
a5f963a
Removing unneeded workflows
Piedone Dec 27, 2022
8097231
Deployment test image
Piedone Dec 28, 2022
0da2b17
Adding deployment workflow
Piedone Dec 28, 2022
69ab833
Renaming test image
Piedone Dec 28, 2022
8ab99a5
Remove unnecessary line break
Piedone Dec 28, 2022
9b140a1
Fixing solution
Piedone Dec 28, 2022
1bd2ba2
Removing test image
Piedone Dec 28, 2022
3636780
Adding test script for remote deployment
Piedone Dec 28, 2022
d675a5f
Test template change
Piedone Dec 28, 2022
5ab5f3c
Revert "Test template change"
Piedone Dec 28, 2022
db2f743
Add build workflow
Piedone Dec 28, 2022
cbff01f
Adding spell-checker ignores
Piedone Dec 28, 2022
293c1d0
More ignore
Piedone Dec 28, 2022
82e6b54
Removing now unneeded base theme config from deployment
Piedone Dec 28, 2022
ff7263a
Ignoring leftover Media Theme deployment folders too
Piedone Dec 28, 2022
2f9e89a
Test CSS change
Piedone Dec 28, 2022
33242c3
Revert "Test CSS change"
Piedone Dec 28, 2022
3475a5b
Using Liquid link tags for link tags
Piedone Dec 28, 2022
d2c5439
Cache busting for links
Piedone Dec 28, 2022
78e396d
Test template change
Piedone Dec 28, 2022
ceef8bf
Revert "Test template change"
Piedone Dec 28, 2022
9a7883d
Test template change
Piedone Jan 3, 2023
9a3fb94
Revert "Test template change"
Piedone Jan 3, 2023
57a57c1
Testing new Spelling workflow
Piedone Jan 4, 2023
b5f4820
Revert "Testing new Spelling workflow"
Piedone Jan 4, 2023
41f424f
Removing issue branch reference
Piedone Jan 5, 2023
3fda6ca
Merge remote-tracking branch 'official/dev' into dev-piedone
Piedone Jan 5, 2023
3136b38
Test template change
Piedone Jan 5, 2023
a69f2aa
Revert "Test template change"
Piedone Jan 5, 2023
291ef7b
Test CSS change
Piedone Jan 5, 2023
1b908a9
Again
Piedone Jan 5, 2023
3dc2e48
Renaming CSS to unstuck it form cache
Piedone Jan 5, 2023
a90f538
Removing debug CSS
Piedone Jan 5, 2023
83656d5
Debug CSS
Piedone Jan 5, 2023
c32efb6
Removing debug CSS
Piedone Jan 5, 2023
1df1085
Debug Layout
Piedone Jan 7, 2023
d65458e
Revert "Debug Layout"
Piedone Jan 7, 2023
7a1c4c2
CSS test
Piedone Jan 8, 2023
1a65035
Revert "CSS test"
Piedone Jan 8, 2023
b4ba47a
Debug template change
Piedone Jan 9, 2023
02e0a42
Revert "Debug template change"
Piedone Jan 9, 2023
151285c
Updating export recipe
Piedone Jan 9, 2023
6c6d763
Updated export with search (but without Elasticsearch)
Piedone Jan 9, 2023
d85a0c6
Removing unnecessary "disable" section from the features export
Piedone Jan 9, 2023
791253b
Fixing search result item link styling
Piedone Jan 9, 2023
8bc5314
Merge remote-tracking branch 'official/dev' into dev-piedone
Piedone Jan 9, 2023
7f7c334
Dummy template change
Piedone Jan 10, 2023
e853a9e
Revert "Dummy template change"
Piedone Jan 10, 2023
02edd24
Using the home background image on every letter
Piedone Jan 15, 2023
fbc843e
Merge remote-tracking branch 'official/dev' into dev-piedone
Piedone Jan 24, 2023
8bbcfb1
Adding ico favicon too
Piedone Jan 24, 2023
0fffed7
Merge remote-tracking branch 'origin/dev-piedone' into dev-piedone
Piedone Jan 24, 2023
580d726
Updating blog posts from prod site
Piedone Jan 24, 2023
05539ec
Removing unneeded admin theme config
Piedone Jan 24, 2023
5ea4304
Updating export recipe with hard-coded content item IDs and user refe…
Piedone Jan 24, 2023
5eb7c80
Dummy change to kick off build
Piedone Jan 31, 2023
17f2b38
Revert "Dummy change to kick off build"
Piedone Jan 31, 2023
642524a
Dummy change to kick off theme deployment
Piedone Jan 31, 2023
7625049
Revert "Dummy change to kick off theme deployment"
Piedone Jan 31, 2023
7db8086
Test Liquid change
Piedone Jan 31, 2023
adc568a
Revert "Test Liquid change"
Piedone Jan 31, 2023
b5046f4
Merge remote-tracking branch 'official/dev' into dev-piedone
Piedone Jan 18, 2024
b9c9596
Fixing spelling
Piedone Jan 18, 2024
6a6c161
Updating gitignore for the latest OC version
Piedone Jan 18, 2024
e80aa75
Temporarily fixing dotnest-consolidate
Piedone Jan 18, 2024
8ddd238
Consolidating packages
Piedone Jan 18, 2024
41e0d96
Revert "Temporarily fixing dotnest-consolidate"
Piedone Jan 18, 2024
f29585e
Removing WTF csproj elements
Piedone Jan 18, 2024
7f72ac0
Merge remote-tracking branch 'official/dev' into dev-piedone
Piedone Jan 26, 2024
7482d56
Post-merge sln fix
Piedone Jan 26, 2024
3e742b3
Consolidating packages
Piedone Jan 26, 2024
9064709
Better UI testing config
Piedone Jan 26, 2024
882a92d
Changing UI testing config to target Letters from Fiume
Piedone Jan 26, 2024
f6132d6
Merge remote-tracking branch 'sdk/issue/SITE-62-uitt-config' into tas…
Piedone Jan 26, 2024
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/build-and-test.yml
Original file line number Diff line number Diff line change
@@ -1,11 +1,10 @@
name: Build and Test

# Runs for PRs opened for any branch, and pushes to the dev branch.
on:
pull_request:
push:
branches:
- dev
- dev-piedone

jobs:
build-and-test:
Expand All @@ -20,3 +19,4 @@ jobs:
with:
additional-dictionaries: |
lombiq-lgha:dictionaries/Liquid.txt
cspell:html/dict/html.txt
24 changes: 0 additions & 24 deletions .github/workflows/create-jira-issues-for-community-activities.yml

This file was deleted.

18 changes: 18 additions & 0 deletions .github/workflows/deploy-theme.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
name: Deploy Media Theme to DotNest

on:
push:
branches:
- dev-piedone
paths:
- 'src/Themes/LettersFromFiume.Theme/**'

jobs:
deploy-media-theme:
uses: Lombiq/Hosting-Media-Theme/.github/workflows/deploy-media-theme.yml@dev
secrets:
URL: ${{ secrets.LETTERS_FROM_FIUME_DEPLOYMENT_URL }}
CLIENT_NAME: ${{ secrets.LETTERS_FROM_FIUME_DEPLOYMENT_CLIENT_NAME }}
CLIENT_API_KEY: ${{ secrets.LETTERS_FROM_FIUME_DEPLOYMENT_CLIENT_API_KEY }}
with:
theme-path: "src/Themes/LettersFromFiume.Theme"
11 changes: 0 additions & 11 deletions .github/workflows/validate-pull-request.yml

This file was deleted.

5 changes: 3 additions & 2 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ artifacts/
node_modules/
*.user
.pnpm-debug.log
src/*/wwwroot/is-cache
src/*/wwwroot/*/is-cache
*.placeholder
App_Data/
*.user
Expand All @@ -26,4 +26,5 @@ profiling/
.build/
.testPublish/

src/*.Web/Localization
src/*.Web/Localization
MediaThemeDeployment_*
4 changes: 2 additions & 2 deletions License.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
Copyright © 2022, [Lombiq Technologies Ltd.](https://lombiq.com)
Copyright © 2022, Zoltán Lehóczky<!-- #spell-check-ignore-line -->

All rights reserved.

Expand All @@ -10,4 +10,4 @@ Redistribution and use in source and binary forms, with or without modification,

* Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
13 changes: 13 additions & 0 deletions LombiqLicense.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
Copyright © 2022, [Lombiq Technologies Ltd.](https://lombiq.com)

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

* Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
12 changes: 9 additions & 3 deletions DotNest.Core.SDK.sln → Piedone.DotNestSites.sln
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ EndProject
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Solution Items", "Solution Items", "{7C140F40-3A44-4A05-BD18-E59431FAD8BE}"
ProjectSection(SolutionItems) = preProject
License.md = License.md
LombiqLicense.md = LombiqLicense.md
NuGet.config = NuGet.config
Readme.md = Readme.md
EndProjectSection
Expand All @@ -23,13 +24,14 @@ EndProject
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "workflows", "workflows", "{190B979E-A5AB-42A4-85CE-8A94044706DF}"
ProjectSection(SolutionItems) = preProject
.github\workflows\build-and-test.yml = .github\workflows\build-and-test.yml
.github\workflows\create-jira-issues-for-community-activities.yml = .github\workflows\create-jira-issues-for-community-activities.yml
.github\workflows\validate-pull-request.yml = .github\workflows\validate-pull-request.yml
.github\workflows\deploy-theme.yml = .github\workflows\deploy-theme.yml
EndProjectSection
EndProject
Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "LettersFromFiume.Theme", "src\Themes\LettersFromFiume.Theme\LettersFromFiume.Theme.csproj", "{CF03AC33-7CCB-49C0-8700-DB1FF18E2E90}"
EndProject
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "test", "test", "{7BE78863-16CE-4AA3-8C46-7761183142DB}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "DotNest.Core.SDK.Tests.UI", "test\DotNest.Core.SDK.Tests.UI\DotNest.Core.SDK.Tests.UI.csproj", "{13764086-2125-4C44-AFC2-665AC3C89AC0}"
Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "DotNest.Core.SDK.Tests.UI", "test\DotNest.Core.SDK.Tests.UI\DotNest.Core.SDK.Tests.UI.csproj", "{13764086-2125-4C44-AFC2-665AC3C89AC0}"
EndProject
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Expand All @@ -45,6 +47,10 @@ Global
{2A65FF2E-0C9C-4FEF-9136-B575141355AE}.Debug|Any CPU.Build.0 = Debug|Any CPU
{2A65FF2E-0C9C-4FEF-9136-B575141355AE}.Release|Any CPU.ActiveCfg = Release|Any CPU
{2A65FF2E-0C9C-4FEF-9136-B575141355AE}.Release|Any CPU.Build.0 = Release|Any CPU
{CF03AC33-7CCB-49C0-8700-DB1FF18E2E90}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{CF03AC33-7CCB-49C0-8700-DB1FF18E2E90}.Debug|Any CPU.Build.0 = Debug|Any CPU
{CF03AC33-7CCB-49C0-8700-DB1FF18E2E90}.Release|Any CPU.ActiveCfg = Release|Any CPU
{CF03AC33-7CCB-49C0-8700-DB1FF18E2E90}.Release|Any CPU.Build.0 = Release|Any CPU
{13764086-2125-4C44-AFC2-665AC3C89AC0}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{13764086-2125-4C44-AFC2-665AC3C89AC0}.Debug|Any CPU.Build.0 = Debug|Any CPU
{13764086-2125-4C44-AFC2-665AC3C89AC0}.Release|Any CPU.ActiveCfg = Release|Any CPU
Expand Down
65 changes: 4 additions & 61 deletions Readme.md
Original file line number Diff line number Diff line change
@@ -1,65 +1,8 @@
# DotNest Core SDK
# DotNest Sites of Zoltán Lehóczky<!-- #spell-check-ignore-line -->

## Overview

[DotNest Core SDK](https://github.com/Lombiq/DotNest-Core-SDK) is a local development environment for building [Media Themes](https://github.com/Lombiq/Hosting-Media-Theme) to be deployed to [Orchard Core CMS](http://orchardcore.net) sites running on [DotNest](http://dotnest.com), the Orchard SaaS. Media Themes are almost full-fledged Orchard themes that you can develop as any Orchard theme, but they'll still work on DotNest.

The base of the source code on the `dev` branch is the same Orchard Core version that is running on DotNest as well as all the hotfixes and mods we've applied to it. On top of that, all the open-source modules are added as NuGet packages, which gives you the ability to develop your theme and run your site locally in an environment quite close to the live DotNest site.

We at [Lombiq](https://lombiq.com/) also used this SDK for the following projects:

- The new [Xero4PowerBI website](https://xero4powerbi.com/) ([see case study](https://dotnest.com/blog/xero4powerbi-website-case-study-migration-to-orchard-core)).<!-- #spell-check-ignore-line -->
- The new [Ik wil een taart website](https://ikwileentaart.nl/) ([see case study](https://dotnest.com/blog/revamping-ik-wil-een-taart-migrating-an-old-version-of-orchard-core-website-with-custom-theme-and-commerce-logic-to-dotnest)).<!-- #spell-check-ignore-line -->
- The new [Show Orchard website](https://showorchard.com/) when migrating it from Orchard 1 DotNest to DotNest Core (see [case study](https://dotnest.com/blog/show-orchard-case-study-migrating-an-orchard-1-dotnest-site-to-orchard-core) and the [theme's source code](https://github.com/Lombiq/Show-Orchard-Theme)).<!-- #spell-check-ignore-line -->

This project, along with DotNest, is developed by [Lombiq Technologies Ltd](https://lombiq.com). Commercial-grade support is available through Lombiq.

## Getting started

Are you unfamiliar with Orchard Core theme development and Liquid templates, or even Orchard Core in general? Then we recommend you check out the [Dojo Course 3 tutorial](https://orcharddojo.net/orchard-training/dojo-course-3-the-full-orchard-core-tutorial) and the official docs [on Liquid](https://docs.orchardcore.net/en/latest/docs/reference/modules/Liquid/) and [templates in Orchard Core](https://docs.orchardcore.net/en/latest/docs/reference/modules/Templates/) first. Otherwise, please continue below.

We have everything documented here, but if you prefer videos, check out our [DotNest Core tutorials here](https://www.youtube.com/playlist?list=PLuskKJW0FhJebHGSavU5OJugryMPCSKaU).

1. Go to GitHub and fork the [DotNest Core SDK](https://github.com/Lombiq/DotNest-Core-SDK) repository or create an empty repository and push the SDK's `dev` branch to it. For simplicity, we'll refer to your repository as `fork` from now on and assume a simple branching strategy with only one additional branch for development, but your use-case can be more complex.
2. For clarity, rename the solution file to what you prefer, e.g. _AwesomeProject.DotNestSites.sln_.
3. Create a project for your theme, as you'd usually do, with [the Orchard code generation template](https://docs.orchardcore.net/en/latest/docs/getting-started/templates/), manually, or by copying `Sample.Theme` from the SDK. The only thing important is that you'll need to add a NuGet package reference to `Lombiq.Hosting.MediaTheme` to it, and in its `Manifest` should declare `Lombiq.Hosting.MediaTheme.Bridge` as a dependency. See `Sample.Theme` for these.
4. Reference the theme project from the root web project, `DotNest.Core.SDK.Web`.
5. You're now good to continue with developing your theme and deploying it to your DotNest site. Continue with the below sections.

You can see an example of a fork of this project for the website [Letters from Fiume](https://lettersfromfiume.com/), with a Media Theme [here](https://github.com/Piedone/DotNest-Sites). This demonstrates how to have a Media Theme theme project with Liquid templates and CSS, and do local development with an export of the production site, also making use of [Auto Setup](https://docs.orchardcore.net/en/latest/docs/reference/modules/AutoSetup/).

### Automatic sync for your fork with Git-hg Mirror

Optionally, you can set up a mirror on [Git-hg Mirror](https://githgmirror.com) to automatically (and continuously) synchronize every commit from the original repository to your fork. This gives you an easy way to always work with same code base as what is running on DotNest.

- The "Git clone URL" should be `git+https://github.com/Lombiq/DotNest-Core-SDK.git`.
- The "Hg clone URL" (don't worry about "Hg") should be a similar URL pointing to your fork with some authentication details to allow Git-hg Mirror to push to your repository. You can create an access token under [your GitHub settings](https://github.com/settings/tokens) (select full `repo` access) and use it as follows: `git+https://0123456789abcdef0123456789abcdef:x-oauth-basic@github.com/AwesomeDeveloper/Awesome-Project.git`.
- The "Mirroring direction" should be `Git to Hg`.
- You'll just need the default branch, so configure "Git ref selection regex for pushes" as `refs/heads/dev`.
- Make sure that you never commit anything to the branches coming from the original repository, otherwise the synchronization will fail.

**Note** that this project uses [GitHub Actions](https://github.com/features/actions) for automated builds. If you don't need these, and especially if your fork will be auto-updated with Git-hg Mirror (which pushes to your repository multiple times a minute) then you shouldn't enable GitHub Actions for the repository (since then e.g. a build will run on each Git-hg Mirror push).

## Working with the repository

- Whenever you create any branches, make sure that you prefix their names so they don't collide with the ones in the SDK.
For example, if the project you're working is called `Awesome Project`, then your development branch should be created on top of `dev` and name it e.g. `ap-dev`.
- You might also want to change the default branch of your fork to your development branch.
- In case new commits are pushed to your fork from the original repository, check the changes (e.g. new modules might be added that you also need to add to your custom solution) and merge `dev` to your development branch.

## Theme development

- General Orchard Core theme development rules apply but with [Media Theme practices](https://github.com/Lombiq/Hosting-Media-Theme#local-development) and [Media Theme limitations](https://github.com/Lombiq/Hosting-Media-Theme#limitations). Keep those in mind.
- You can synchronize content from your site running on DotNest by exporting it and then importing it locally. That way, you can maintain a setup recipe locally that you keep up-to-date with the production site's data, even using [Auto Setup](https://docs.orchardcore.net/en/latest/docs/reference/modules/AutoSetup/).
to set up the site when you run the app. Be sure to not use the recipe locally without some modifications:
- Remove feature `enable` references for all Azure-related features unless you want to use e.g. Azure Blob Storage locally too.
- Enable your theme project and set it as the site theme (instead of Media Theme).
- Deploy your theme to your site by following [the corresponding docs of Media Theme](https://github.com/Lombiq/Hosting-Media-Theme/blob/dev/Readme.md#deployment-importexport).

The [`Piedone/DotNest-Sites` project](https://github.com/Piedone/DotNest-Sites) mentioned above also demonstrates all of these.<!-- #spell-check-ignore-line -->

## Help us make it better!
## Overview

In case you come across an Orchard Core bug during development, don't keep it to yourself: Orchard Core bugs should be reported at [the official Orchard Core GitHub repository](https://github.com/OrchardCMS/OrchardCore).
Code for my websites on the Orchard Core SaaS [DotNest](https://dotnest.com/).

There is a chance though that the problem you've discovered is already fixed since the latest release and we could add the necessary changes as a hotfix to DotNest (and the DotNest Core SDK) to improve it. You can tell us about it by opening an issue in [the DotNest Core SDK GitHub repository](https://github.com/Lombiq/DotNest-Core-SDK). Thanks!
- [Letters from Fiume](https://lettersfromfiume.com/): My personal website and blog.
6 changes: 4 additions & 2 deletions src/DotNest.Core.SDK.Web/DotNest.Core.SDK.Web.csproj
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
<Project Sdk="Microsoft.NET.Sdk.Web">
<Project Sdk="Microsoft.NET.Sdk.Web">

<PropertyGroup>
<TargetFramework>net6.0</TargetFramework>
Expand Down Expand Up @@ -35,11 +35,13 @@
<PackageReference Include="Lombiq.SetupExtensions" Version="5.0.0" />
<PackageReference Include="Lombiq.Hosting.MediaTheme" Version="5.0.1-alpha.1.osoe-775" />
<PackageReference Include="Lombiq.Hosting.MediaTheme.Bridge" Version="5.0.1-alpha.1.osoe-775" />
<PackageReference Include="Lombiq.Tests.UI.Shortcuts" Version="8.2.1-alpha.6.osoe-351" />
<PackageReference Include="Lombiq.Tests.UI.AppExtensions" Version="8.2.1-alpha.13.tdeal-16" />
<PackageReference Include="Lombiq.Tests.UI.Shortcuts" Version="8.2.1-alpha.13.tdeal-16" />
<PackageReference Include="Lombiq.Walkthroughs" Version="1.0.0-alpha.1.lmbq-113" />
</ItemGroup>

<ItemGroup>
<ProjectReference Include="..\Themes\Sample.Theme\Sample.Theme.csproj" />
<ProjectReference Include="..\Themes\LettersFromFiume.Theme\LettersFromFiume.Theme.csproj" />
</ItemGroup>
</Project>
13 changes: 3 additions & 10 deletions src/DotNest.Core.SDK.Web/Program.cs
Original file line number Diff line number Diff line change
Expand Up @@ -12,18 +12,11 @@
builder.Services
.AddSingleton(configuration)
.AddOrchardCms(orchardCoreBuilder =>
{
orchardCoreBuilder
.AddDatabaseShellsConfigurationIfAvailable(configuration)
.ConfigureSmtpSettings(overrideAdminSettings: false);

if (builder.Environment.IsDevelopment())
{
orchardCoreBuilder
.AddSetupFeatures("OrchardCore.AutoSetup")
.HideRecipesByTagsFromSetup("test", "HideFromSetupScreen");
}
});
.ConfigureSmtpSettings(overrideAdminSettings: false)
.EnableAutoSetupIfNotUITesting(configuration)
.HideRecipesByTagsFromSetup("test", "HideFromSetupScreen"));

var app = builder.Build();

Expand Down
Loading
Loading