The s3 server (currently seaweedfs) needs to have a public url, because a user's browser needs to talk to it directly. Perhaps just serve it on /s3/*?
Also, note that we then do need to make it mandatory to set the secret properly (deploy/s3config.json).
The s3 server (currently seaweedfs) needs to have a public url, because a user's browser needs to talk to it directly. Perhaps just serve it on /s3/*?
Also, note that we then do need to make it mandatory to set the secret properly (deploy/s3config.json).