From 90db45d8450220e77d972569b665fb3c4185e5fa Mon Sep 17 00:00:00 2001 From: Manav Rathi Date: Sat, 25 May 2024 08:35:22 +0530 Subject: [PATCH] uploading --- docs/docs/self-hosting/guides/configuring-s3.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/docs/self-hosting/guides/configuring-s3.md b/docs/docs/self-hosting/guides/configuring-s3.md index 0ea93f75e..56e922f02 100644 --- a/docs/docs/self-hosting/guides/configuring-s3.md +++ b/docs/docs/self-hosting/guides/configuring-s3.md @@ -91,9 +91,9 @@ To fix these, you should ensure the following: 1. The bucket CORS rules do not allow museum to access these objects. - > For viewing the uploaded files from the browser, you will need to - > currently set allowedOrigins to "\*", and allow the "X-Auth-Token", - > "X-Client-Package" headers configuration too. + > For uploading files from the browser, you will need to currently set + > allowedOrigins to "\*", and allow the "X-Auth-Token", "X-Client-Package" + > headers configuration too. > [Here is an example of a working configuration](https://github.com/ente-io/ente/discussions/1764#discussioncomment-9478204). 2. The credentials are not being picked up (you might be setting the correct