diff --git a/assets/scss/_oss_health.scss b/assets/scss/_oss_health.scss index 4fae99dcb..ad9664a74 100644 --- a/assets/scss/_oss_health.scss +++ b/assets/scss/_oss_health.scss @@ -176,6 +176,20 @@ color: #fff; } } + + // Three 7rem buttons don't fit on phones and push the page sideways. + @include media-breakpoint-down(lg) { + display: flex; + max-width: 100%; + width: 100%; + + &__button { + flex: 1 1 0; + min-width: 0; + padding-left: 0.5rem; + padding-right: 0.5rem; + } + } } .oss-health-grid { diff --git a/assets/scss/_page.scss b/assets/scss/_page.scss index 3ad264318..6a6292568 100644 --- a/assets/scss/_page.scss +++ b/assets/scss/_page.scss @@ -86,3 +86,9 @@ } } } + +// Long URLs and inline-code links in docs and blog posts must wrap, +// otherwise they overflow the viewport on mobile. +.td-content a { + overflow-wrap: anywhere; +} diff --git a/assets/scss/blocks/_hero.scss b/assets/scss/blocks/_hero.scss index 292033c53..639177ee6 100644 --- a/assets/scss/blocks/_hero.scss +++ b/assets/scss/blocks/_hero.scss @@ -3,8 +3,10 @@ @include td-box-height-modifiers(".td-hero-block"); .hero-gitops { - margin-left: -15px; - margin-right: -15px; + // Match Bootstrap 5 gutter (0.75rem). The old -15px was the Bootstrap 4 value + // and made the page 3px wider than the viewport (horizontal scroll). + margin-left: -0.75rem; + margin-right: -0.75rem; @include media-breakpoint-down(md) { padding: 0 15px; diff --git a/content/de/support.md b/content/de/support.md index 48c4705bb..f7ec7bd7b 100644 --- a/content/de/support.md +++ b/content/de/support.md @@ -4,7 +4,7 @@ date: 2025-03-02T15:45:07+04:00 draft: false type: "page" weight: 50 -source_digest: "sha256:2cacdfc9855cebb5b4df0c21de9b889985cba9754a72581f10f1cd5ea6a0c286" +source_digest: "sha256:de998fb26d73dc851cf18a0437e5f7d1397e551876c7d8742e14f7816ae57ac8" translation_status: current l10n: mt --- @@ -13,4 +13,4 @@ l10n: mt | Organisation | Kontakt | Leistungsbeschreibung | | ------------ | ------- | ------------------ | | Aenix logo | [Website](https://aenix.io/contact/) [LinkedIn](https://www.linkedin.com/company/aenix-io)| Wir bieten jede Art von Unterstützung: Beratung, Entwicklung fehlender Funktionen, Design sowie Hilfe bei Installation und Integration. | -| Hidora | [Website](https://hidora.io/en/contact/) [LinkedIn](https://www.linkedin.com/company/hidora)| Wir übernehmen die Installation, bieten laufenden Support und Managed Services rund um die Uhr (24/7). | +| Hidora | [Website](https://hidora.io/en/contact/) [LinkedIn](https://www.linkedin.com/company/hidora)| Wir übernehmen die Installation, bieten laufenden Support und Managed Services rund um die Uhr (24/7). | diff --git a/content/en/blog/2025-12-17-talm-v0-17-built-in-age-encryption-for-secrets.md b/content/en/blog/2025-12-17-talm-v0-17-built-in-age-encryption-for-secrets.md index 9b39cae12..c4a196aaa 100644 --- a/content/en/blog/2025-12-17-talm-v0-17-built-in-age-encryption-for-secrets.md +++ b/content/en/blog/2025-12-17-talm-v0-17-built-in-age-encryption-for-secrets.md @@ -4,8 +4,6 @@ slug: talm-v0-17-built-in-age-encryption-for-secrets date: 2025-12-17 author: "Andrei Kvapil (Ænix)" description: "Talm v0.17 introduces built-in age encryption for secure secrets management, making it easier to store sensitive configuration files in Git repositories while maintaining security best practices." -images: - - "https://cdn-images-1.medium.com/max/800/0*encryption.png" article_types: - release topics: @@ -18,8 +16,6 @@ topics: The latest release of [Talm](https://github.com/cozystack/talm), the configuration manager for Talos Linux, introduces a powerful new feature: built-in encryption using the [age](https://age-encryption.org/) encryption tool. This enhancement allows you to securely store sensitive configuration files like `secrets.yaml`, `talosconfig`, and `kubeconfig` in Git repositories while following security best practices. -![](https://cdn-images-1.medium.com/max/800/0*encryption.png) - ### Why Age Encryption? Managing secrets in Git repositories has always been a challenge. While storing configuration files in version control is convenient for GitOps workflows, sensitive data like API keys, certificates, and cluster credentials should never be committed in plain text. Traditional solutions like `git-crypt` or external secret management systems add complexity and dependencies. diff --git a/content/en/docs/next/operations/oidc/identity_providers/google.md b/content/en/docs/next/operations/oidc/identity_providers/google.md index 324c1647b..0c091937e 100644 --- a/content/en/docs/next/operations/oidc/identity_providers/google.md +++ b/content/en/docs/next/operations/oidc/identity_providers/google.md @@ -10,19 +10,19 @@ aliases: ## Configure Google - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project. -![1](/img/oidc/identity_providers/google/1.jpeg) +![1](/img/OIDC/identity_providers/google/1.jpeg) - Click on "New Project" to proceed. -![2](/img/oidc/identity_providers/google/2.jpeg) +![2](/img/OIDC/identity_providers/google/2.jpeg) - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create" -![3](/img/oidc/identity_providers/google/3.jpeg) +![3](/img/OIDC/identity_providers/google/3.jpeg) - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step. -![4](/img/oidc/identity_providers/google/4.jpeg) +![4](/img/OIDC/identity_providers/google/4.jpeg) - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create". -![5](/img/oidc/identity_providers/google/5.jpeg) +![5](/img/OIDC/identity_providers/google/5.jpeg) - After this, we will be redirected to pages where we will have to configure different things - Application type: Public @@ -32,16 +32,16 @@ aliases: - Application Privacy Policy link: Your application privacy policy link - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID". -![6](/img/oidc/identity_providers/google/6.jpeg) +![6](/img/OIDC/identity_providers/google/6.jpeg) - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this ```bash https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint ``` -![7](/img/oidc/identity_providers/google/7.jpeg) +![7](/img/OIDC/identity_providers/google/7.jpeg) - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it. -![8](/img/oidc/identity_providers/google/8.jpeg) +![8](/img/OIDC/identity_providers/google/8.jpeg) ## Configure Keycloak Identity Provider Create a `KeycloakRealmIdentityProvider` resource with the following configuration: diff --git a/content/en/docs/v0/operations/oidc/identity_providers/google.md b/content/en/docs/v0/operations/oidc/identity_providers/google.md index 5251b6e6b..3248c527a 100644 --- a/content/en/docs/v0/operations/oidc/identity_providers/google.md +++ b/content/en/docs/v0/operations/oidc/identity_providers/google.md @@ -12,19 +12,19 @@ aliases: ## Configure Google - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project. -![1](/img/oidc/identity_providers/google/1.jpeg) +![1](/img/OIDC/identity_providers/google/1.jpeg) - Click on "New Project" to proceed. -![2](/img/oidc/identity_providers/google/2.jpeg) +![2](/img/OIDC/identity_providers/google/2.jpeg) - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create" -![3](/img/oidc/identity_providers/google/3.jpeg) +![3](/img/OIDC/identity_providers/google/3.jpeg) - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step. -![4](/img/oidc/identity_providers/google/4.jpeg) +![4](/img/OIDC/identity_providers/google/4.jpeg) - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create". -![5](/img/oidc/identity_providers/google/5.jpeg) +![5](/img/OIDC/identity_providers/google/5.jpeg) - After this, we will be redirected to pages where we will have to configure different things - Application type: Public @@ -34,16 +34,16 @@ aliases: - Application Privacy Policy link: Your application privacy policy link - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID". -![6](/img/oidc/identity_providers/google/6.jpeg) +![6](/img/OIDC/identity_providers/google/6.jpeg) - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this ```bash https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint ``` -![7](/img/oidc/identity_providers/google/7.jpeg) +![7](/img/OIDC/identity_providers/google/7.jpeg) - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it. -![8](/img/oidc/identity_providers/google/8.jpeg) +![8](/img/OIDC/identity_providers/google/8.jpeg) ## Configure Keycloak Identity Provider Create a `KeycloakRealmIdentityProvider` resource with the following configuration: diff --git a/content/en/docs/v1.0/operations/oidc/identity_providers/google.md b/content/en/docs/v1.0/operations/oidc/identity_providers/google.md index c152f341f..187b0a29b 100644 --- a/content/en/docs/v1.0/operations/oidc/identity_providers/google.md +++ b/content/en/docs/v1.0/operations/oidc/identity_providers/google.md @@ -10,19 +10,19 @@ aliases: ## Configure Google - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project. -![1](/img/oidc/identity_providers/google/1.jpeg) +![1](/img/OIDC/identity_providers/google/1.jpeg) - Click on "New Project" to proceed. -![2](/img/oidc/identity_providers/google/2.jpeg) +![2](/img/OIDC/identity_providers/google/2.jpeg) - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create" -![3](/img/oidc/identity_providers/google/3.jpeg) +![3](/img/OIDC/identity_providers/google/3.jpeg) - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step. -![4](/img/oidc/identity_providers/google/4.jpeg) +![4](/img/OIDC/identity_providers/google/4.jpeg) - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create". -![5](/img/oidc/identity_providers/google/5.jpeg) +![5](/img/OIDC/identity_providers/google/5.jpeg) - After this, we will be redirected to pages where we will have to configure different things - Application type: Public @@ -32,16 +32,16 @@ aliases: - Application Privacy Policy link: Your application privacy policy link - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID". -![6](/img/oidc/identity_providers/google/6.jpeg) +![6](/img/OIDC/identity_providers/google/6.jpeg) - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this ```bash https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint ``` -![7](/img/oidc/identity_providers/google/7.jpeg) +![7](/img/OIDC/identity_providers/google/7.jpeg) - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it. -![8](/img/oidc/identity_providers/google/8.jpeg) +![8](/img/OIDC/identity_providers/google/8.jpeg) ## Configure Keycloak Identity Provider Create a `KeycloakRealmIdentityProvider` resource with the following configuration: diff --git a/content/en/docs/v1.1/operations/oidc/identity_providers/google.md b/content/en/docs/v1.1/operations/oidc/identity_providers/google.md index 9db96aceb..0c3e014cc 100644 --- a/content/en/docs/v1.1/operations/oidc/identity_providers/google.md +++ b/content/en/docs/v1.1/operations/oidc/identity_providers/google.md @@ -10,19 +10,19 @@ aliases: ## Configure Google - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project. -![1](/img/oidc/identity_providers/google/1.jpeg) +![1](/img/OIDC/identity_providers/google/1.jpeg) - Click on "New Project" to proceed. -![2](/img/oidc/identity_providers/google/2.jpeg) +![2](/img/OIDC/identity_providers/google/2.jpeg) - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create" -![3](/img/oidc/identity_providers/google/3.jpeg) +![3](/img/OIDC/identity_providers/google/3.jpeg) - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step. -![4](/img/oidc/identity_providers/google/4.jpeg) +![4](/img/OIDC/identity_providers/google/4.jpeg) - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create". -![5](/img/oidc/identity_providers/google/5.jpeg) +![5](/img/OIDC/identity_providers/google/5.jpeg) - After this, we will be redirected to pages where we will have to configure different things - Application type: Public @@ -32,16 +32,16 @@ aliases: - Application Privacy Policy link: Your application privacy policy link - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID". -![6](/img/oidc/identity_providers/google/6.jpeg) +![6](/img/OIDC/identity_providers/google/6.jpeg) - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this ```bash https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint ``` -![7](/img/oidc/identity_providers/google/7.jpeg) +![7](/img/OIDC/identity_providers/google/7.jpeg) - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it. -![8](/img/oidc/identity_providers/google/8.jpeg) +![8](/img/OIDC/identity_providers/google/8.jpeg) ## Configure Keycloak Identity Provider Create a `KeycloakRealmIdentityProvider` resource with the following configuration: diff --git a/content/en/docs/v1.2/operations/oidc/identity_providers/google.md b/content/en/docs/v1.2/operations/oidc/identity_providers/google.md index 4ec804dc0..51f949c65 100644 --- a/content/en/docs/v1.2/operations/oidc/identity_providers/google.md +++ b/content/en/docs/v1.2/operations/oidc/identity_providers/google.md @@ -10,19 +10,19 @@ aliases: ## Configure Google - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project. -![1](/img/oidc/identity_providers/google/1.jpeg) +![1](/img/OIDC/identity_providers/google/1.jpeg) - Click on "New Project" to proceed. -![2](/img/oidc/identity_providers/google/2.jpeg) +![2](/img/OIDC/identity_providers/google/2.jpeg) - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create" -![3](/img/oidc/identity_providers/google/3.jpeg) +![3](/img/OIDC/identity_providers/google/3.jpeg) - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step. -![4](/img/oidc/identity_providers/google/4.jpeg) +![4](/img/OIDC/identity_providers/google/4.jpeg) - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create". -![5](/img/oidc/identity_providers/google/5.jpeg) +![5](/img/OIDC/identity_providers/google/5.jpeg) - After this, we will be redirected to pages where we will have to configure different things - Application type: Public @@ -32,16 +32,16 @@ aliases: - Application Privacy Policy link: Your application privacy policy link - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID". -![6](/img/oidc/identity_providers/google/6.jpeg) +![6](/img/OIDC/identity_providers/google/6.jpeg) - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this ```bash https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint ``` -![7](/img/oidc/identity_providers/google/7.jpeg) +![7](/img/OIDC/identity_providers/google/7.jpeg) - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it. -![8](/img/oidc/identity_providers/google/8.jpeg) +![8](/img/OIDC/identity_providers/google/8.jpeg) ## Configure Keycloak Identity Provider Create a `KeycloakRealmIdentityProvider` resource with the following configuration: diff --git a/content/en/docs/v1.3/operations/oidc/identity_providers/google.md b/content/en/docs/v1.3/operations/oidc/identity_providers/google.md index 23ee6ff40..6414413ab 100644 --- a/content/en/docs/v1.3/operations/oidc/identity_providers/google.md +++ b/content/en/docs/v1.3/operations/oidc/identity_providers/google.md @@ -10,19 +10,19 @@ aliases: ## Configure Google - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project. -![1](/img/oidc/identity_providers/google/1.jpeg) +![1](/img/OIDC/identity_providers/google/1.jpeg) - Click on "New Project" to proceed. -![2](/img/oidc/identity_providers/google/2.jpeg) +![2](/img/OIDC/identity_providers/google/2.jpeg) - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create" -![3](/img/oidc/identity_providers/google/3.jpeg) +![3](/img/OIDC/identity_providers/google/3.jpeg) - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step. -![4](/img/oidc/identity_providers/google/4.jpeg) +![4](/img/OIDC/identity_providers/google/4.jpeg) - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create". -![5](/img/oidc/identity_providers/google/5.jpeg) +![5](/img/OIDC/identity_providers/google/5.jpeg) - After this, we will be redirected to pages where we will have to configure different things - Application type: Public @@ -32,16 +32,16 @@ aliases: - Application Privacy Policy link: Your application privacy policy link - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID". -![6](/img/oidc/identity_providers/google/6.jpeg) +![6](/img/OIDC/identity_providers/google/6.jpeg) - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this ```bash https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint ``` -![7](/img/oidc/identity_providers/google/7.jpeg) +![7](/img/OIDC/identity_providers/google/7.jpeg) - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it. -![8](/img/oidc/identity_providers/google/8.jpeg) +![8](/img/OIDC/identity_providers/google/8.jpeg) ## Configure Keycloak Identity Provider Create a `KeycloakRealmIdentityProvider` resource with the following configuration: diff --git a/content/en/docs/v1.4/operations/oidc/identity_providers/google.md b/content/en/docs/v1.4/operations/oidc/identity_providers/google.md index 88a316634..367f9c7ab 100644 --- a/content/en/docs/v1.4/operations/oidc/identity_providers/google.md +++ b/content/en/docs/v1.4/operations/oidc/identity_providers/google.md @@ -10,19 +10,19 @@ aliases: ## Configure Google - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project. -![1](/img/oidc/identity_providers/google/1.jpeg) +![1](/img/OIDC/identity_providers/google/1.jpeg) - Click on "New Project" to proceed. -![2](/img/oidc/identity_providers/google/2.jpeg) +![2](/img/OIDC/identity_providers/google/2.jpeg) - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create" -![3](/img/oidc/identity_providers/google/3.jpeg) +![3](/img/OIDC/identity_providers/google/3.jpeg) - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step. -![4](/img/oidc/identity_providers/google/4.jpeg) +![4](/img/OIDC/identity_providers/google/4.jpeg) - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create". -![5](/img/oidc/identity_providers/google/5.jpeg) +![5](/img/OIDC/identity_providers/google/5.jpeg) - After this, we will be redirected to pages where we will have to configure different things - Application type: Public @@ -32,16 +32,16 @@ aliases: - Application Privacy Policy link: Your application privacy policy link - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID". -![6](/img/oidc/identity_providers/google/6.jpeg) +![6](/img/OIDC/identity_providers/google/6.jpeg) - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this ```bash https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint ``` -![7](/img/oidc/identity_providers/google/7.jpeg) +![7](/img/OIDC/identity_providers/google/7.jpeg) - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it. -![8](/img/oidc/identity_providers/google/8.jpeg) +![8](/img/OIDC/identity_providers/google/8.jpeg) ## Configure Keycloak Identity Provider Create a `KeycloakRealmIdentityProvider` resource with the following configuration: diff --git a/content/en/docs/v1.5/operations/oidc/identity_providers/google.md b/content/en/docs/v1.5/operations/oidc/identity_providers/google.md index 3fb94effb..774b10545 100644 --- a/content/en/docs/v1.5/operations/oidc/identity_providers/google.md +++ b/content/en/docs/v1.5/operations/oidc/identity_providers/google.md @@ -10,19 +10,19 @@ aliases: ## Configure Google - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project. -![1](/img/oidc/identity_providers/google/1.jpeg) +![1](/img/OIDC/identity_providers/google/1.jpeg) - Click on "New Project" to proceed. -![2](/img/oidc/identity_providers/google/2.jpeg) +![2](/img/OIDC/identity_providers/google/2.jpeg) - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create" -![3](/img/oidc/identity_providers/google/3.jpeg) +![3](/img/OIDC/identity_providers/google/3.jpeg) - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step. -![4](/img/oidc/identity_providers/google/4.jpeg) +![4](/img/OIDC/identity_providers/google/4.jpeg) - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create". -![5](/img/oidc/identity_providers/google/5.jpeg) +![5](/img/OIDC/identity_providers/google/5.jpeg) - After this, we will be redirected to pages where we will have to configure different things - Application type: Public @@ -32,16 +32,16 @@ aliases: - Application Privacy Policy link: Your application privacy policy link - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID". -![6](/img/oidc/identity_providers/google/6.jpeg) +![6](/img/OIDC/identity_providers/google/6.jpeg) - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this ```bash https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint ``` -![7](/img/oidc/identity_providers/google/7.jpeg) +![7](/img/OIDC/identity_providers/google/7.jpeg) - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it. -![8](/img/oidc/identity_providers/google/8.jpeg) +![8](/img/OIDC/identity_providers/google/8.jpeg) ## Configure Keycloak Identity Provider Create a `KeycloakRealmIdentityProvider` resource with the following configuration: diff --git a/content/en/docs/v1.6/operations/oidc/identity_providers/google.md b/content/en/docs/v1.6/operations/oidc/identity_providers/google.md index 9b9c135f1..9e64c222b 100644 --- a/content/en/docs/v1.6/operations/oidc/identity_providers/google.md +++ b/content/en/docs/v1.6/operations/oidc/identity_providers/google.md @@ -10,19 +10,19 @@ aliases: ## Configure Google - Head over to [Google Console](https://console.cloud.google.com/apis/dashboard), login in to the console using Google account and you will see Google Developer Console. Once logged in, head over the top left drop-down to create new project. -![1](/img/oidc/identity_providers/google/1.jpeg) +![1](/img/OIDC/identity_providers/google/1.jpeg) - Click on "New Project" to proceed. -![2](/img/oidc/identity_providers/google/2.jpeg) +![2](/img/OIDC/identity_providers/google/2.jpeg) - Enter the project name of your choice and select the Organisation if you have multiple organisations. Once done click on "Create" -![3](/img/oidc/identity_providers/google/3.jpeg) +![3](/img/OIDC/identity_providers/google/3.jpeg) - Once the project is created you will get a pop-up suggesting to configure the consent screen. If not then head over to the Dashboard and head over to "Explore and enable APIs" options. Then Click on "Credentials" > "Configure Consent Screen" and head over to the next step. -![4](/img/oidc/identity_providers/google/4.jpeg) +![4](/img/OIDC/identity_providers/google/4.jpeg) - Click on "External" as we want to allow any Google account to be able to sign in to our application and hit "Create". -![5](/img/oidc/identity_providers/google/5.jpeg) +![5](/img/OIDC/identity_providers/google/5.jpeg) - After this, we will be redirected to pages where we will have to configure different things - Application type: Public @@ -32,16 +32,16 @@ aliases: - Application Privacy Policy link: Your application privacy policy link - Now head over to the Create Credentials option in the navbar and click on "OAuth Client ID". -![6](/img/oidc/identity_providers/google/6.jpeg) +![6](/img/OIDC/identity_providers/google/6.jpeg) - Select Application type as a "Web application" and name the application according to your choice. Next, Add the link provided in the Keycloak tab under "Authorized Redirect URIs" and click "Create". The link should look something like this ```bash https://YOUR_KEYCLOAK_DOMAIN/auth/realms/cozy/broker/google/endpoint ``` -![7](/img/oidc/identity_providers/google/7.jpeg) +![7](/img/OIDC/identity_providers/google/7.jpeg) - As it is done, you will see a pop up with the information required in the next step. You will need to "Client ID" and "Client secret" in next step so make sure you make a safe copy of it. -![8](/img/oidc/identity_providers/google/8.jpeg) +![8](/img/OIDC/identity_providers/google/8.jpeg) ## Configure Keycloak Identity Provider Create a `KeycloakRealmIdentityProvider` resource with the following configuration: diff --git a/content/en/support.md b/content/en/support.md index 579241902..375668f31 100644 --- a/content/en/support.md +++ b/content/en/support.md @@ -10,4 +10,4 @@ weight: 50 | Organization | Contact | Description of Use | | ------------ | ------- | ------------------ | | Aenix logo | [Site](https://aenix.io/contact/) [LinkedIn](https://www.linkedin.com/company/aenix-io)| We provide all types of assistance, including consultations, development of missing features, design, assistance with installation, and integration. | -| Hidora | [Site](https://hidora.io/en/contact/) [LinkedIn](https://www.linkedin.com/company/hidora)| We handle installation, provide ongoing support, and offer 24/7 managed services. | +| Hidora | [Site](https://hidora.io/en/contact/) [LinkedIn](https://www.linkedin.com/company/hidora)| We handle installation, provide ongoing support, and offer 24/7 managed services. | diff --git a/content/hi/support.md b/content/hi/support.md index 5b6ff2f8f..095b80161 100644 --- a/content/hi/support.md +++ b/content/hi/support.md @@ -4,7 +4,7 @@ date: 2025-03-02T15:45:07+04:00 draft: false type: "page" weight: 50 -source_digest: "sha256:2cacdfc9855cebb5b4df0c21de9b889985cba9754a72581f10f1cd5ea6a0c286" +source_digest: "sha256:de998fb26d73dc851cf18a0437e5f7d1397e551876c7d8742e14f7816ae57ac8" translation_status: current l10n: mt --- @@ -13,4 +13,4 @@ l10n: mt | संगठन | संपर्क | सेवा का विवरण | | ------------ | ------- | ------------------ | | Aenix logo | [साइट](https://aenix.io/contact/) [LinkedIn](https://www.linkedin.com/company/aenix-io)| हम हर प्रकार की सहायता प्रदान करते हैं, जिसमें परामर्श, अनुपलब्ध सुविधाओं का विकास, डिज़ाइन, तथा इंस्टॉलेशन और एकीकरण में सहायता शामिल है। | -| Hidora | [साइट](https://hidora.io/en/contact/) [LinkedIn](https://www.linkedin.com/company/hidora)| हम इंस्टॉलेशन संभालते हैं, निरंतर सहायता देते हैं, और 24/7 मैनेज्ड सेवाएँ प्रदान करते हैं। | +| Hidora | [साइट](https://hidora.io/en/contact/) [LinkedIn](https://www.linkedin.com/company/hidora)| हम इंस्टॉलेशन संभालते हैं, निरंतर सहायता देते हैं, और 24/7 मैनेज्ड सेवाएँ प्रदान करते हैं। | diff --git a/content/ru/support.md b/content/ru/support.md index 290810ed1..5034ea9d1 100644 --- a/content/ru/support.md +++ b/content/ru/support.md @@ -4,7 +4,7 @@ date: 2025-03-02T15:45:07+04:00 draft: false type: "page" weight: 50 -source_digest: "sha256:2cacdfc9855cebb5b4df0c21de9b889985cba9754a72581f10f1cd5ea6a0c286" +source_digest: "sha256:de998fb26d73dc851cf18a0437e5f7d1397e551876c7d8742e14f7816ae57ac8" translation_status: current l10n: mt --- @@ -13,4 +13,4 @@ l10n: mt | Организация | Контакт | Описание услуг | | ------------ | ------- | ------------------ | | Aenix logo | [Сайт](https://aenix.io/contact/) [LinkedIn](https://www.linkedin.com/company/aenix-io)| Мы оказываем все виды помощи: консультации, разработку недостающих функций, проектирование, помощь с установкой и интеграцией. | -| Hidora | [Сайт](https://hidora.io/en/contact/) [LinkedIn](https://www.linkedin.com/company/hidora)| Мы выполняем установку, обеспечиваем постоянную поддержку и предлагаем managed-сервисы в режиме 24/7. | +| Hidora | [Сайт](https://hidora.io/en/contact/) [LinkedIn](https://www.linkedin.com/company/hidora)| Мы выполняем установку, обеспечиваем постоянную поддержку и предлагаем managed-сервисы в режиме 24/7. | diff --git a/content/zh-cn/support.md b/content/zh-cn/support.md index ca2ae3cde..ab386e4a2 100644 --- a/content/zh-cn/support.md +++ b/content/zh-cn/support.md @@ -4,7 +4,7 @@ date: 2025-03-02T15:45:07+04:00 draft: false type: "page" weight: 50 -source_digest: "sha256:2cacdfc9855cebb5b4df0c21de9b889985cba9754a72581f10f1cd5ea6a0c286" +source_digest: "sha256:de998fb26d73dc851cf18a0437e5f7d1397e551876c7d8742e14f7816ae57ac8" translation_status: current l10n: mt --- @@ -13,4 +13,4 @@ l10n: mt | 组织 | 联系方式 | 服务说明 | | ------------ | ------- | ------------------ | | Aenix logo | [网站](https://aenix.io/contact/) [LinkedIn](https://www.linkedin.com/company/aenix-io)| 我们提供各类支持，包括咨询、缺失功能的开发、设计，以及安装与集成方面的协助。 | -| Hidora | [网站](https://hidora.io/en/contact/) [LinkedIn](https://www.linkedin.com/company/hidora)| 我们负责安装、提供持续支持，并提供 7×24 小时托管服务。 | +| Hidora | [网站](https://hidora.io/en/contact/) [LinkedIn](https://www.linkedin.com/company/hidora)| 我们负责安装、提供持续支持，并提供 7×24 小时托管服务。 | diff --git a/layouts/shortcodes/home/screenshot-gallery.html b/layouts/shortcodes/home/screenshot-gallery.html index e3f83ca26..ca5071acc 100644 --- a/layouts/shortcodes/home/screenshot-gallery.html +++ b/layouts/shortcodes/home/screenshot-gallery.html @@ -110,4 +110,20 @@

{{ T "home_screenshots" }}

background-color: #1a73e8; transform: scale(1.15); } + +/* On phones the screenshot is short, so 16 dots overlay its content. + Move them below the image and make them smaller. */ +@media (max-width: 767.98px) { + .screenshot-gallery .carousel-indicators { + position: static; + margin-top: 1rem; + gap: 6px; + flex-wrap: wrap; + } + + .screenshot-gallery .carousel-indicators [data-bs-target] { + width: 8px; + height: 8px; + } +} diff --git a/static/img/logos/hidora.svg b/static/img/logos/hidora.svg new file mode 100644 index 000000000..6d5216405 --- /dev/null +++ b/static/img/logos/hidora.svg @@ -0,0 +1,33 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +