Ability to configure S3 base url

[nkt]

In case you want to upload artifacts to S3-compatible (not S3) service (minio for example), you have to configure base url, but it is impossible for now.

[graywolf336]

My vote is for this issue, would love to have this as we are looking into using Minio.

[develar]

Could you please provide information why S3 or DO Spaces is not suitable for you?

[develar]

Fixed in 19.45.0

Don't forget to add Read Only policy for Minio bucket otherwise public URLs will not work (critical for auto-updater).

[graywolf336]

@develar The reason S3 or DO Spaces is not suitable is because we are trying to keep our costs down, yes the cost of each of them is extremely low but when you don't have a budget (like on a side project) then just throwing up a docker image on an existing system is simple enough.

Thanks for adding this though, I appreciate it!

[develar]

... and in this case you don't need to reinvent the wheel implementing own uploading service and HTTP public API. Thanks for explanation. I will add note about Minio to docs.

[JPorter44]

@develar I am just trying to set up the localhost server to test auto updating with Electron and was curious where you navigate to in order to change the read only policy. I am new to Minio and don't really know much about it.

[rajivshah3]

@JPorter44 if you log in to the browser access URL given by MinIO and hover over the bucket name in the left sidebar, three dots will appear. You can click those and then click "Edit policy"