11
Customizable "send" URL
Source: dani-garcia/vaultwarden#4361 · opened by @ajgon
So here is my use-case - I have my whole vaultwarden instance hidden inside my private network. However it would be great, to expose send links (and only them) to the Internet in case I wish to share something with somebody who is not connected to my VPN. Currently send links are just root (/) slashes with some hashtag-javascript-magic, which will require me to expose whole vaultwarden basically.
Would it be possible, to have a configurable "send" path? Or (if it's easier) configurable "send" domain? Currently I have separate domain for "send" and it works like a charm, but I have to manually copy the link every time, replace the main vaultwarden domain with "send" domain, and then send a link which is cumbersome.
Thank you, for this amazing project!
Would it be possible, to have a configurable "send" path? Or (if it's easier) configurable "send" domain? Currently I have separate domain for "send" and it works like a charm, but I have to manually copy the link every time, replace the main vaultwarden domain with "send" domain, and then send a link which is cumbersome.
Thank you, for this amazing project!
No pledges yet. Be the first to back this.
Comments
Similar requests
Feature Request: User-based Permissions for “Send” Feature
1 vote · 0 comments
Feature Request: User-based Permissions for “Send” Feature
2 votes · 0 comments
Email notification to the Send owner when a Send gets downloaded
2 votes · 0 comments
Allow /send/ to be exposed on a separate port while keeping Vaultwarden internal
1 vote · 0 comments
Proposal: Share an existing Login item as a structured temporary Send link
1 vote · 0 comments
No comments yet.