Skip to content

Add Neon Object Storage to destination constants - #5951

Open
rishi-raj-jain wants to merge 1 commit into
Dokploy:canaryfrom
rishi-raj-jain:patch-1
Open

rishi-raj-jain wants to merge 1 commit into
Dokploy:canaryfrom
rishi-raj-jain:patch-1

Conversation

@rishi-raj-jain

@rishi-raj-jain rishi-raj-jain commented Nov 10, 2026 •

Copy link
Copy Markdown

What is this PR about?

Adds Neon Object Storage to one of the S3 destinations.

Neon is now a first party integration in 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 canary 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)

Screenshots (if applicable)

RetriggerView in GreptileConfidence Score: 5/5

The PR appears safe to merge; no actionable issues were established.

Summary

Adds Neon Object Storage to the destination provider dropdown.

  • Users can choose Neon Object Storage as an S3 destination.

Reviews (1) · Last reviewed commit: "Add Neon Object Storage to destination c..." · Reviewed by Greptile

This branch has not been deployed

No deployments
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