You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding a guide how to use the AWS S3 command line correctly to upload a static website to be able to host e.g SvelteKit on Edge Services. An example GitHub action can be added as well.
Why is it needed?
I figured out the endpoint displayed in the object storage dashboard is confusing. An example is:
https://mybucket.s3.fr-par.scw.cloud
When uploading to this bucket using the CLI, e.g using the following command:
A folder will be created under https://mybucket.s3.fr-par.scw.cloud/mybucket.
Since the Edge Service serves from the bucket's root directory, it is not possible to use the service in this way. Instead one needs to upload to the root endpoint of the region:
A guide or otherwise any mention of this in the documentation would have saved me an investigation of multiple hours, that was only resolved by diffing the URL created by the web UI vs the command line.
Hello,
Sorry for the late reply: we would be happy for you to go ahead and write this tutorial.
Please feel free to open a PR whenever you are ready :-)
Summary
Adding a guide how to use the AWS S3 command line correctly to upload a static website to be able to host e.g SvelteKit on Edge Services. An example GitHub action can be added as well.
Why is it needed?
I figured out the endpoint displayed in the object storage dashboard is confusing. An example is:
When uploading to this bucket using the CLI, e.g using the following command:
A folder will be created under
https://mybucket.s3.fr-par.scw.cloud/mybucket
.Since the Edge Service serves from the bucket's root directory, it is not possible to use the service in this way. Instead one needs to upload to the root endpoint of the region:
A guide or otherwise any mention of this in the documentation would have saved me an investigation of multiple hours, that was only resolved by diffing the URL created by the web UI vs the command line.
Want to write this documentation yourself?
Yes
Related PR(s)
No response
(Optional) Scaleway Organization ID
No response
Email address
[email protected]
The text was updated successfully, but these errors were encountered: