Suggestion: Make the base URL configurable and prefix optional #114
Replies: 4 comments 1 reply
-
Hey @maxacarvalho! I 100% agree that I think that would be a really useful feature. I've actually been working on a project myself that would probably benefit from this type of functionality in the future. I'm more than happy to accept a PR for this functionality if you fancy making one 😄 |
Beta Was this translation helpful? Give feedback.
-
would really really love this feature |
Beta Was this translation helpful? Give feedback.
-
These changes should all be available from v7.0.0 onwards 😄 |
Beta Was this translation helpful? Give feedback.
-
Is there any documentation available on how to use this feature? Wanted to use a custom domain for the short url e.g. tinylink.co/asdf I saw that the PR #121 should have added the functionality for that, but not sure how to set the custom domain. i have a route setup already, but don't know how to set the domain before its generated. The route setup I currently have:
this is the output of my
The routing works, but the |
Beta Was this translation helpful? Give feedback.
-
Hello,
Thanks for your solution, it's very nice.
I'd like to make a suggestion, to let the application users to choose the base URL and make the prefix optional.
At the moment, I can see that the
default_sort_url
is set toconfig('app.url').'/'.$this->prefix().'/'.$this->urlKey
, which makes impossible to have a domain different than the application one for the shortened URL.Use case:
Let's say I have a full domain app that's https://full-domain-app.com, but when shortening the URL, I want to use
https://fda.is
, so the URL is even shorter. Let's say I also want to remove theprefix
altogether.Something like this could do the trick:
I could create a PR for that, but I think it's better to understand if that's something you would like to add to your package.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions