Skip to content

docs: add Neon Object Storage S3 destination guide - #230

Open
rishi-raj-jain wants to merge 5 commits into
Dokploy:mainfrom
rishi-raj-jain:main
Open

rishi-raj-jain wants to merge 5 commits into
Dokploy:mainfrom
rishi-raj-jain:main

Conversation

@rishi-raj-jain

Copy link
Copy Markdown

What is this PR about?

Adds a Neon Object Storage page under S3 Destinations, following the existing Cloudflare R2 page.

Follow-up to Dokploy/dokploy#5951, where it was pointed out that Neon Object Storage already works with the Any other S3 compatible provider option. Rather than adding a new provider, this documents how to set it up with that option.

The page covers:

  • Creating a bucket and a credential with storage:read and storage:write scopes in the Neon Console
  • Where to find the branch endpoint and region
  • How each value maps to the Dokploy destination form (Access Key Id, Secret Access Key, Region, Endpoint, Bucket)

No additional flags are needed, since Dokploy already passes --s3-force-path-style to rclone.

Disclaimer: I work as a contractor for Neon.

Checklist

Before submitting this PR, please make sure that:

  • You created a dedicated branch based on the main branch.
  • You have read the suggestions in the CONTRIBUTING.md file https://github.com/Dokploy/dokploy/blob/canary/CONTRIBUTING.md#pull-request
  • You have tested this PR in your local instance. If you have not tested it yet, please do so before submitting. This helps avoid wasting maintainers' time reviewing code that has not been verified by you.

Issues related (if applicable)

Related to Dokploy/dokploy#5951

Screenshots (if applicable)

@rishi-raj-jain

Copy link
Copy Markdown
Author

Also, Neon is happy to co-market if that seems like a nice value exchange for the docs addition! We'll do a guide on https://neon.com/guides linking back to Dokploy!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant