Go to file

Jim Johnston 18a60e2d2e docs: S3 providers - add example for DigitalOcean Spaces endpoint (#10145 )

The [S3 providers docs](https://docs.medusajs.com/resources/architectural-modules/file/s3#:R1d5rtttqj5db:) instructs DigitalOcean users to set the endpoint address to the "Spaces Origin Endpoint":
```
For DigitalOcean Spaces, it's the Spaces Origin Endpoint.
```

On DigitalOcean's user interface they include the bucket name in their origin endpoint:
![image](https://github.com/user-attachments/assets/e4c6ab05-ff1c-40ad-bb2b-49653b990e6b)

Using this url for the endpoint will cause an error.

The example URL `https://{region}.digitaloceanspaces.com` should tip users off to remove the bucketname.

Cheers!

2024-11-19 10:52:26 +00:00

.changeset

fix(payment): Idempotent cancellation and proper creationg fail handling (#10135 )

2024-11-18 17:45:13 +00:00

.github

docs: update to next 15 + eslint 9 (#9839 )

2024-11-13 17:03:17 +02:00

.yarn

fix(ui): Bump cva and minor type fixes (#5818 )

2023-12-07 20:13:44 +00:00

integration-tests

feat(medusa, types, utils, core-flows, order) request & accept order transfer (#10106 )

2024-11-19 08:53:22 +00:00

packages

feat(medusa, types, utils, core-flows, order) request & accept order transfer (#10106 )

2024-11-19 08:53:22 +00:00

scripts

chore: dependecies reorg (#8535 )

2024-08-23 07:16:04 -03:00

www

docs: S3 providers - add example for DigitalOcean Spaces endpoint (#10145 )

2024-11-19 10:52:26 +00:00

_tsconfig.base.json

feat(framework,medusa): Ensure publishable key middleware is set for all store endpoints (#9429 )

2024-10-02 18:01:50 +02:00

.eslintignore

fea(providers): locking postgres (#9545 )

2024-10-17 13:11:39 +00:00

.eslintrc.js

fea(providers): locking postgres (#9545 )

2024-10-17 13:11:39 +00:00

.gitattributes

…

.gitignore

feat(locking): Locking module (#9524 )

2024-10-11 16:30:06 +00:00

.prettierrc

…

.vale.ini

docs: prep for v2 documentation (#6710 )

2024-03-18 07:47:35 +00:00

.yarnrc.yml

…

CHANGELOG.md

…

CODEOWNERS

feat(admin-sdk,admin-bundler,admin-shared,medusa): Restructure admin packages (#8988 )

2024-09-04 19:00:25 +00:00

CONTRIBUTING.md

chore: Update contibuting with new branching strategy (#7193 )

2024-05-01 13:50:02 +02:00

define_jest_config.js

chore: swc/jest source maps config to inline instead of true (#9531 )

2024-10-11 09:40:51 +02:00

jest.config.js

chore(medusa): cleanup medusa package (#7206 )

2024-05-07 12:48:49 +02:00

LICENSE

…

package.json

chore: remove husky (#9967 )

2024-11-07 07:54:30 +00:00

README.md

chore: update doc links in README (#9860 )

2024-11-10 08:58:19 +01:00

SECURITY.md

…

turbo.json

fix: bust cache builds (#6847 )

2024-03-27 17:46:32 +01:00

yarn.lock

chore: Release

2024-11-12 10:12:48 +01:00

Medusa

Getting Started

Visit the Documentation to set up a Medusa application.

What is Medusa

Medusa is a set of commerce modules and tools that allow you to build rich, reliable, and performant commerce applications without reinventing core commerce logic. The modules can be customized and used to build advanced ecommerce stores, marketplaces, or any product that needs foundational commerce primitives. All modules are open-source and freely available on npm.

Learn more about Medusa’s architecture and commerce modules in the Docs.

Roadmap, Upgrades & Integrations

You can view the planned, started and completed features in the Roadmap discussion.

Follow the Release Notes to keep your Medusa project up-to-date.

Check out all available Medusa integrations.

Community & Contributions

The community and core team are available in GitHub Discussions, where you can ask for support, discuss roadmap, and share ideas.

Our Contribution Guide describes how to contribute to the codebase and Docs.

Join our Discord server to meet other community members.

Other channels

License

Licensed under the MIT License.

README.md Unescape Escape