From 8cef69384be9f06e685afee4e43a21737784a949 Mon Sep 17 00:00:00 2001 From: selmankoc Date: Wed, 23 Oct 2024 15:59:43 +0300 Subject: [PATCH] Fixed paths of images --- .../step1-create-azure-resources.md | 36 +++++++++---------- .../step3-deployment-github-action.md | 16 ++++----- .../deployment/deployment-docker-compose.md | 4 +-- .../deployment/deployment-iis.md | 10 +++--- .../deployment/identityserver-deployment.md | 10 +++--- .../deployment/openiddict-deployment.md | 4 +-- 6 files changed, 40 insertions(+), 40 deletions(-) diff --git a/docs/en/solution-templates/layered-web-application/deployment/azure-deployment/step1-create-azure-resources.md b/docs/en/solution-templates/layered-web-application/deployment/azure-deployment/step1-create-azure-resources.md index a818c1287d..4a4601486c 100644 --- a/docs/en/solution-templates/layered-web-application/deployment/azure-deployment/step1-create-azure-resources.md +++ b/docs/en/solution-templates/layered-web-application/deployment/azure-deployment/step1-create-azure-resources.md @@ -25,7 +25,7 @@ To create a new Azure Web App Service, choose one of the following options: 3. Search for **Web App** and select **Web App** from the results. - ![Create a resource](../../../images/azure-deploy-create-a-resource.png) + ![Create a resource](../../../../images/azure-deploy-create-a-resource.png) 4. Click the **Create** button. @@ -33,11 +33,11 @@ To create a new Azure Web App Service, choose one of the following options: 6. Click the **Create** button. - ![Create Web App](../../../images/azure-deploy-create-web-app-2.png) + ![Create Web App](../../../../images/azure-deploy-create-web-app-2.png) 7. Wait for the deployment to complete. - ![Create Web App](../../../images/azure-deploy-create-web-app-3.png) + ![Create Web App](../../../../images/azure-deploy-create-web-app-3.png) {{else}} @@ -51,7 +51,7 @@ To create a new Azure Web App Service, choose one of the following options: 3. Search for **Web App** and select **Web App** from the results. - ![Create a resource](../../../images/azure-deploy-create-a-resource.png) + ![Create a resource](../../../../images/azure-deploy-create-a-resource.png) 4. Click the **Create** button. @@ -59,11 +59,11 @@ To create a new Azure Web App Service, choose one of the following options: 6. Click the **Create** button. - ![Create Web App](../../../images/azure-deploy-create-web-app-2.png) + ![Create Web App](../../../../images/azure-deploy-create-web-app-2.png) 7. Wait for the deployment to complete. - ![Create Web App](../../../images/azure-deploy-create-web-app-3.png) + ![Create Web App](../../../../images/azure-deploy-create-web-app-3.png) {{ else if UI == 'NG' }} @@ -75,7 +75,7 @@ To create a new Azure Web App Service, choose one of the following options: 3. Search for **Static Web App** and select **Static Web App** from the results. - ![Create a resource angular](../../../images/azure-deploy-create-a-resource-angular.png) + ![Create a resource angular](../../../../images/azure-deploy-create-a-resource-angular.png) 4. Click the **Create** button. @@ -83,11 +83,11 @@ To create a new Azure Web App Service, choose one of the following options: 6. Click the **Create** button. - ![Create Web App](../../../images/azure-deploy-create-web-app-4.png) + ![Create Web App](../../../../images/azure-deploy-create-web-app-4.png) 7. Wait for the deployment to complete. - ![Create Web App](../../../images/azure-deploy-create-web-app-5.png) + ![Create Web App](../../../../images/azure-deploy-create-web-app-5.png) {{else}} @@ -99,7 +99,7 @@ To create a new Azure Web App Service, choose one of the following options: 3. Search for **Static Web App** and select **Static Web App** from the results. - ![Create a resource blazor](../../../images/azure-deploy-create-a-resource-angular.png) + ![Create a resource blazor](../../../../images/azure-deploy-create-a-resource-angular.png) 4. Click the **Create** button. @@ -107,11 +107,11 @@ To create a new Azure Web App Service, choose one of the following options: 6. Click the **Create** button. - ![Create Web App](../../../images/azure-deploy-create-web-app-7.png) + ![Create Web App](../../../../images/azure-deploy-create-web-app-7.png) 7. Wait for the deployment to complete. - ![Create Web App](../../../images/azure-deploy-create-web-app-8.png) + ![Create Web App](../../../../images/azure-deploy-create-web-app-8.png) {{end}} @@ -123,7 +123,7 @@ To create a new Azure Web App Service, choose one of the following options: 3. Search for **Web App** and select **Web App** from the results. - ![Create a resource](../../../images/azure-deploy-create-a-resource.png) + ![Create a resource](../../../../images/azure-deploy-create-a-resource.png) 4. Click the **Create** button. @@ -131,11 +131,11 @@ To create a new Azure Web App Service, choose one of the following options: 6. Click the **Create** button. - ![Create Web App](../../../images/azure-deploy-create-web-app-6.png) + ![Create Web App](../../../../images/azure-deploy-create-web-app-6.png) 7. Wait for the deployment to complete. - ![Create Web App](../../../images/azure-deploy-create-web-app-3.png) + ![Create Web App](../../../../images/azure-deploy-create-web-app-3.png) {{ if Tiered == "Yes" && (UI == "MVC" || UI == "BlazorServer")}} @@ -151,7 +151,7 @@ Same as above, but you only need to modify the name of the web app service to ** 2. Search for **Redis Cache** and select **Redis Cache** from the results. - ![Create a resource](../../../images/azure-deploy-create-redis.png) + ![Create a resource](../../../../images/azure-deploy-create-redis.png) 3. Click the **Create** button. @@ -159,11 +159,11 @@ Same as above, but you only need to modify the name of the web app service to ** 5. Click the **Create** button. - ![Create Redis](../../../images/azure-deploy-create-redis-2.png) + ![Create Redis](../../../../images/azure-deploy-create-redis-2.png) 6. Wait for the deployment to complete. - ![Create Redis](../../../images/azure-deploy-create-redis-3.png) + ![Create Redis](../../../../images/azure-deploy-create-redis-3.png) {{ end }} diff --git a/docs/en/solution-templates/layered-web-application/deployment/azure-deployment/step3-deployment-github-action.md b/docs/en/solution-templates/layered-web-application/deployment/azure-deployment/step3-deployment-github-action.md index 32e51a2a58..9aa9e5df83 100644 --- a/docs/en/solution-templates/layered-web-application/deployment/azure-deployment/step3-deployment-github-action.md +++ b/docs/en/solution-templates/layered-web-application/deployment/azure-deployment/step3-deployment-github-action.md @@ -19,7 +19,7 @@ 4. Click the **set up a workflow yourself** button. - ![Set up this workflow](../../../images/azure-deploy-set-up-this-workflow.png) + ![Set up this workflow](../../../../images/azure-deploy-set-up-this-workflow.png) 5. Copy this content to the opened file and commit it. @@ -685,7 +685,7 @@ jobs: 9. Click the **New repository secret** button. - ![New repository secret](../../../images/azure-deploy-new-repository-secret.png) + ![New repository secret](../../../../images/azure-deploy-new-repository-secret.png) 10. Add the following secrets: @@ -693,17 +693,17 @@ jobs: Example of Azure SQL connection string: - ![Azure sql connection string](../../../images/azure-deploy-connection-string.png) + ![Azure sql connection string](../../../../images/azure-deploy-connection-string.png) - **AZUREAPPSERVICE_PUBLISHPROFILE**: The publish the profile of your Azure Web App Service. You can download it from the **Overview** tab of your Azure Web App Service. - ![Publish profile](../../../images/azure-deploy-publish-profile.png) + ![Publish profile](../../../../images/azure-deploy-publish-profile.png) {{ if UI == "NG" || UI == "Blazor"}} - **AZURE_STATIC_WEB_APPS_API_TOKEN_AMBITIOUS**: The API token of your Azure Static Web App. You can get it from the **Overview** tab of your Azure Static Web App. - ![API token](../../../images/azure-deploy-api-token.png) + ![API token](../../../../images/azure-deploy-api-token.png) {{end}} @@ -711,15 +711,15 @@ jobs: 12. Click the **Deploy to Azure Web App** workflow. - ![Deploy to Azure Web App](../../../images/azure-deploy-deploy-to-azure-web-app.png) + ![Deploy to Azure Web App](../../../../images/azure-deploy-deploy-to-azure-web-app.png) 13. Click the **Run workflow** button. - ![Run workflow](../../../images/azure-deploy-run-workflow.png) + ![Run workflow](../../../../images/azure-deploy-run-workflow.png) 14. Navigate to the web app URL to see the deployed application. - ![Azure Web App](../../../images/azure-deploy-runtime-stack2.png) + ![Azure Web App](../../../../images/azure-deploy-runtime-stack2.png) > If deploying your application was unsuccessful, you can check the logs of the deployment by clicking the **Deploy to Azure Web App** workflow and then clicking the **deploy-to-webapp** job. diff --git a/docs/en/solution-templates/layered-web-application/deployment/deployment-docker-compose.md b/docs/en/solution-templates/layered-web-application/deployment/deployment-docker-compose.md index 6c9c724638..9767beb3ba 100644 --- a/docs/en/solution-templates/layered-web-application/deployment/deployment-docker-compose.md +++ b/docs/en/solution-templates/layered-web-application/deployment/deployment-docker-compose.md @@ -449,7 +449,7 @@ ENTRYPOINT ["dotnet", "Acme.BookStore.Blazor.dll"] You can come across an error when the image is being built. This occurs because of `dotnet dev-certs` command trying to list the existing certificates **inside the container** and unavailable to. This error is not important since we aim to generate the **authserver.pfx** file and discard the container it is built in. -![auth-server-pfx-generation-error](../../../en/images/auth-server-pfx-generation-error.png) +![auth-server-pfx-generation-error](../../../images/auth-server-pfx-generation-error.png) Since it contains the OpenID-provider within, it also uses multi-stages to generate `authserver.pfx` file which is **used by OpenIddict as a signing and encryption certificate**. This configuration is found under the `PreConfigureServices` method of the **BlazorModule**: @@ -794,7 +794,7 @@ ENTRYPOINT ["dotnet", "Acme.BookStore.HttpApi.Host.dll"] You can come across an error when the image is being built. This occurs because of `dotnet dev-certs` command trying to list the existing certificates **inside the container** and unavailable to. This error is not important since we aim to generate the **authserver.pfx** file and discard the container it is built in. -![auth-server-pfx-generation-error](../../../en/images/auth-server-pfx-generation-error.png) +![auth-server-pfx-generation-error](../../../images/auth-server-pfx-generation-error.png) Since it contains the openid-provider within, it also uses multi-stages to generate `authserver.pfx` file which is **used by OpenIddict as a signing and encryption certificate**. This configuration is found under the `PreConfigureServices` method of the **HttpApiHostModule**: diff --git a/docs/en/solution-templates/layered-web-application/deployment/deployment-iis.md b/docs/en/solution-templates/layered-web-application/deployment/deployment-iis.md index 5be87f85cb..ee6f6667c2 100644 --- a/docs/en/solution-templates/layered-web-application/deployment/deployment-iis.md +++ b/docs/en/solution-templates/layered-web-application/deployment/deployment-iis.md @@ -134,7 +134,7 @@ Rename the created file extension to ".pfx" Import the certificate to IIS -![Import the certificate](../../images/iis-install-cert.gif) +![Import the certificate](../../../images/iis-install-cert.gif) ### Add domain names to hosts file @@ -240,19 +240,19 @@ You can add as website from IIS. > For {{ if Tiered == "Yes" }}authserver{{ else if UI == "NG" || UI == "Blazor" }}apihost{{ else if UI == "BlazorServer" }}blazor{{ else }}web{{ end }} we need to enable load user profile to true from application pool for created web site. -![Load User Profile](../../images/load-user-profile-iis.png) +![Load User Profile](../../../images/load-user-profile-iis.png) > For local deployment select the SSL certificate when you add the web site. -![SSL Certificate Selection](../../images/ssl-cert-selection-in-iis.png) +![SSL Certificate Selection](../../../images/ssl-cert-selection-in-iis.png) The final result should look like this (depending on your project type). -![IIS deployment](../../images/iis-sample-deployment.png) +![IIS deployment](../../../images/iis-sample-deployment.png) We can visit the websites from a browser. -![Tiered IIS deployment](../../images/iis-sample-tiered-deployment.gif) +![Tiered IIS deployment](../../../images/iis-sample-tiered-deployment.gif) ## What's next? diff --git a/docs/en/solution-templates/layered-web-application/deployment/identityserver-deployment.md b/docs/en/solution-templates/layered-web-application/deployment/identityserver-deployment.md index b73968c632..8cb9438576 100644 --- a/docs/en/solution-templates/layered-web-application/deployment/identityserver-deployment.md +++ b/docs/en/solution-templates/layered-web-application/deployment/identityserver-deployment.md @@ -24,7 +24,7 @@ This configuration must be done if **Angular** or **Blazor** (web assembly) is u Update DbMigrator project `appsettings.json` **IdentityServer.Clients.RootUrls** with production values: -![db-migrator-appsettings](../../images/db-migrator-appsettings.png) +![db-migrator-appsettings](../../../images/db-migrator-appsettings.png) Or, manually add production values to `IdentityServerClientRedirectUris`, `IdentityServerClientPostLogoutRedirectUris`, `IdentityServerClientCorsOrigins` tables in your database. @@ -42,7 +42,7 @@ Default development environment uses [developer signing certificates option](htt Update **IdentityServerModule** with using real certificate on `IIdentityServerBuilder` pre-configuration. -![idsrv-certificate](../../images/idsrv-certificate.png) +![idsrv-certificate](../../../images/idsrv-certificate.png) You can also [create self-signed certificate](https://docs.abp.io/en/commercial/5.0/startup-templates/microservice/tye-integration#create-developer-certificates) and use it. @@ -52,7 +52,7 @@ You can also [create self-signed certificate](https://docs.abp.io/en/commercial/ Update **IdentityServerModule** to [enfcore https](https://docs.microsoft.com/en-us/aspnet/core/security/enforcing-ssl?view=aspnetcore-6.0&tabs=visual-studio). Add `UseHsts` to add hsts headers to clients, add `UseHttpsRedirection` to redirect http requests to https. -![use-https](../../images/use-https.png) +![use-https](../../../images/use-https.png) ### Behind Load Balancer @@ -70,11 +70,11 @@ app.Use((httpContext, next) => A common scenario is running applications in kubernetes environment. While IdentityServer needs to face internet on https, internal requests can be done using http. -![idsrv-k8s](../../images/idsrv-k8s.png) +![idsrv-k8s](../../../images/idsrv-k8s.png) **HttpApi.Host** and **Web** applications authority should be set to http since token validations will done using http request. -![api-resource-internal-idsrv](../../images/api-resource-internal-idsrv.png) +![api-resource-internal-idsrv](../../../images/api-resource-internal-idsrv.png) > You can use different appsettings files like *appsettings.production.json* to override these values or directly override environment values from kubernetes. diff --git a/docs/en/solution-templates/layered-web-application/deployment/openiddict-deployment.md b/docs/en/solution-templates/layered-web-application/deployment/openiddict-deployment.md index 72608e5ccc..65ac72719c 100644 --- a/docs/en/solution-templates/layered-web-application/deployment/openiddict-deployment.md +++ b/docs/en/solution-templates/layered-web-application/deployment/openiddict-deployment.md @@ -22,7 +22,7 @@ If **Angular** or **Blazor** (Web Assembly) is used as a back-office web applica Update DbMigrator project `appsettings.json` **OpenIddict.Applications.RootUrls** with production values or override them: -![db-migrator-appsettings](../images/db-migrator-openiddict-appsettings.png) +![db-migrator-appsettings](../../../images/db-migrator-openiddict-appsettings.png) > If you are using microservice template self-migration and not using DbMigrator project, update **IdentityService** appsettings. @@ -39,7 +39,7 @@ The default development environment uses [developer signing certificates option] Update **AuthServerModule** by using a real certificate on `OpenIddictBuilder` pre-configuration. -![openiddict-certificate](../images/openiddict-certificate.png) +![openiddict-certificate](../../../images/openiddict-certificate.png) When you create a new application from the application template, ABP CLI automatically generates a new self-signed certificate with the name `openiddict.pfx` and a random password. This file and the password are provided in the `GetSigningCertificate` method.