Multi-Tenancy for internal use #555
Calvin Mayo (AlulaCM)
started this conversation in
Ideas
Replies: 2 comments
|
That's an interesting scenario. Calvin Mayo (@AlulaCM) can you describe how you would like the URL shortener to behave, or what would be the feature you would like to see implemented? |
0 replies
|
Thanks Frank Boucher (@fboucher). So basically, each one of our platforms/solutions would need to call the endpoints to create their own URLs and perform the redirects, which is already technically doable. However, being able to distinguish between different callers is what we need most. Firstly, it's necessary for the apportioning of costs, and secondly, some of our solutions are white labeled, so some customers will choose to use their own domains. If the admin interface could then be updated to show usage and statistics by caller, that would be amazing! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
We develop several products for our customers, and many of them use a URL shortener. Is there a roadmap item to either create or convert this version into a multi-tenant solution that we can run internally?
All reactions