From 16181dd1b91bdecaff9631138d4e6cccb2d16f69 Mon Sep 17 00:00:00 2001 From: Manav Rathi Date: Fri, 6 Sep 2024 09:27:36 +0530 Subject: [PATCH 1/2] [docs] Mention auth s3 --- docs/docs/self-hosting/faq/index.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/docs/self-hosting/faq/index.md b/docs/docs/self-hosting/faq/index.md index b1f0c0d311..9d87205740 100644 --- a/docs/docs/self-hosting/faq/index.md +++ b/docs/docs/self-hosting/faq/index.md @@ -14,7 +14,10 @@ storage namespace. The same user account works for both of them. Yes, if you wish, you can self-host the server and use it only for the 2FA auth app. The starter Docker compose will work fine for either Photos or Auth (or -both!) +both!). + +> You currently don't need to configure the S3 object storage (e.g. minio +> containers) if you're only using your self hosted Ente instance for auth. ### Can I use the server with _X_ as the object storage? From 1571b70716bcad610dac9e63cbec023afb34d5fe Mon Sep 17 00:00:00 2001 From: Manav Rathi Date: Fri, 6 Sep 2024 09:28:09 +0530 Subject: [PATCH 2/2] yarn pretty --- .../auth/troubleshooting/windows-login.md | 55 +++++++++++-------- docs/docs/photos/features/share.md | 4 +- .../self-hosting/guides/configuring-s3.md | 4 +- 3 files changed, 36 insertions(+), 27 deletions(-) diff --git a/docs/docs/auth/troubleshooting/windows-login.md b/docs/docs/auth/troubleshooting/windows-login.md index 2a990fc7af..7459874cec 100644 --- a/docs/docs/auth/troubleshooting/windows-login.md +++ b/docs/docs/auth/troubleshooting/windows-login.md @@ -1,43 +1,52 @@ --- title: Unable to login on Windows Desktop description: - Troubleshooting when you are not able to login or register on Ente Auth app on Windows + Troubleshooting when you are not able to login or register on Ente Auth app + on Windows --- - - # Windows Login Error - ### HandshakeException: Handshake error in client -This error usually happens when the Trusted Root certificates on your Windows machine are outdated. +This error usually happens when the Trusted Root certificates on your Windows +machine are outdated. -To update the Trusted Root Certificates on Windows, you can use the `certutil` command. Here are the steps to do so: +To update the Trusted Root Certificates on Windows, you can use the `certutil` +command. Here are the steps to do so: -1. **Open Command Prompt as Administrator**: - - Press `Windows + X` and select `Command Prompt (Admin)` or `Windows PowerShell (Admin)`. +1. **Open Command Prompt as Administrator**: + + - Press `Windows + X` and select `Command Prompt (Admin)` or + `Windows PowerShell (Admin)`. 2. **Run the following command to update the root certificates**: - ```bash - certutil -generateSSTFromWU roots.sst - ``` - This command will generate a file named `roots.sst` that contains the latest root certificates from Windows Update. + + ```bash + certutil -generateSSTFromWU roots.sst + ``` + + This command will generate a file named `roots.sst` that contains the latest + root certificates from Windows Update. 3. **Install the new root certificates**: - ```bash - certutil -addstore -f ROOT roots.sst - ``` - This command will add the certificates from the `roots.sst` file to the Trusted Root Certification Authorities store. -4. **Clean up**: - After the installation, you can delete the `roots.sst` file if you no longer need it: - ```bash - del roots.sst - ``` + ```bash + certutil -addstore -f ROOT roots.sst + ``` -Make sure to restart your application after updating the certificates to ensure the changes take effect. + This command will add the certificates from the `roots.sst` file to the + Trusted Root Certification Authorities store. -If the above steps don't resolve the issue, please follow [this guide](https://woshub.com/updating-trusted-root-certificates-in-windows-10/#h2_3) to update your trusted root certicates, and try again. +4. **Clean up**: After the installation, you can delete the `roots.sst` file if + you no longer need it: + ```bash + del roots.sst + ``` +Make sure to restart your application after updating the certificates to ensure +the changes take effect. +If the above steps don't resolve the issue, please follow +[this guide](https://woshub.com/updating-trusted-root-certificates-in-windows-10/#h2_3) +to update your trusted root certicates, and try again. diff --git a/docs/docs/photos/features/share.md b/docs/docs/photos/features/share.md index 076b5546e1..6f6201b043 100644 --- a/docs/docs/photos/features/share.md +++ b/docs/docs/photos/features/share.md @@ -74,8 +74,8 @@ items, in case the original owner were to delete it from their own library. We plan to tackle these complexities in the future, by copying a reference to the item that was shared, instead of the actual file, so that your storage will only get consumed if the original owner deletes it from their library. If this -sounds useful to you, please participate in [this -discussion](https://github.com/ente-io/ente/discussions/790). +sounds useful to you, please participate in +[this discussion](https://github.com/ente-io/ente/discussions/790). ## Technical details diff --git a/docs/docs/self-hosting/guides/configuring-s3.md b/docs/docs/self-hosting/guides/configuring-s3.md index dd228741de..37f98d05c8 100644 --- a/docs/docs/self-hosting/guides/configuring-s3.md +++ b/docs/docs/self-hosting/guides/configuring-s3.md @@ -83,8 +83,8 @@ clients (e.g. the mobile app) and also from within the Docker compose cluster. ### Example -An example `museum.yaml` when you're trying to connect to museum running on your computer from your -phone on the same WiFi network: +An example `museum.yaml` when you're trying to connect to museum running on your +computer from your phone on the same WiFi network: ``` s3: