Commit graph

12 commits

Author SHA1 Message Date
Manav Rathi 7ded8ad4fe
Fix key name 2024-03-18 13:07:36 +05:30
Manav Rathi 30cf709eb2
Wrap 2024-03-18 12:39:16 +05:30
Manav Rathi d8347c3976
Remove extra environment 2024-03-18 12:36:29 +05:30
Manav Rathi 5ee878c30e
Require nginx before starting museum.nginx 2024-03-18 12:33:27 +05:30
Manav Rathi f695c5e0d3
Remove extra newline 2024-03-18 11:06:54 +05:30
Manav Rathi 303b26b95f
Tweak the nginx setup 2024-03-18 11:04:31 +05:30
Manav Rathi 9ba9b8a984
Add initial nginx conf 2024-03-18 10:39:39 +05:30
Manav Rathi d893efe5d1
Remove the restart limiter
During recent DDoS attacks, these restart limits had to be manually
disabled. For now, disabling them in our reference copy too, will bring them
back if they are needed later.
2024-03-18 10:27:42 +05:30
Manav Rathi a0599f7b33
Outline the nginx approach 2024-03-18 10:25:11 +05:30
Manav Rathi 9beedcf4e0
Move into separate folder 2024-03-18 10:16:55 +05:30
Manav Rathi 2905315e00
[server] Improve the architecture diagram
Add a dotted arrow between museum and the hot object storage to indicate that
clients talk directly to the primary S3 storage.

This has confused some users who were trying to setup self-hosting, them not
realizing that the minio buckets need to be accessible outside the container.

The actual flow is - for both GET and PUT, museum conjures up pre-signed URLs by
talking to the S3 bucket, and vends these pre-signed URLs back to the
client. Thereafter though (unless routed via a Cloudflare worker, which is not
the case when self-hosting), the clients directly connect to this presigned URL.

Maybe too much information to convey with a single dotted arrow, but at least
it'll give a hint that there is a direct connection there somewhere.
2024-03-14 16:23:53 +05:30
Neeraj Gupta 531bb344fe Import museum 2024-03-01 13:37:01 +05:30