From 6a1f5945b9957191cd5f601a2d882d5136667f30 Mon Sep 17 00:00:00 2001 From: Manav Rathi Date: Sat, 25 May 2024 08:34:36 +0530 Subject: [PATCH] pretty --- docs/docs/self-hosting/guides/configuring-s3.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/docs/self-hosting/guides/configuring-s3.md b/docs/docs/self-hosting/guides/configuring-s3.md index 41230078c..0ea93f75e 100644 --- a/docs/docs/self-hosting/guides/configuring-s3.md +++ b/docs/docs/self-hosting/guides/configuring-s3.md @@ -92,10 +92,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. [Here is an example of a - > working - > configuration](https://github.com/ente-io/ente/discussions/1764#discussioncomment-9478204). + > 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 creds, but not in the place where museum picks them from).