You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey! I wanted to suggest an option for domain specific vanity urls (url shortener).
What does this mean? Pretty simple!
I think I'm not the only person using zipline with multiple domains and the support for it is good so far. But one awesome feature is missing: having an option to select which shortened url corresponds with which domain.
While creating a shortened url and giving it it's own vanity path, it would be awesome if we could also choose for which domain it corresponds (by default it should probably be the main or all)
Let's create a simple scenario everyone understands:
You own 3 domains, for each domain you have your own social media accounts or whatever but for the sake we use a txt file.
2 configured, one not.
example.com/txt -> example.com.txt
example.org/txt -> example.org.txt
Accessing com goes to com.txt, org to org.txt and accessing example.net/txt goes to the main one (let's say com.txt)
This way no one would need multiple instances just for the shortener or something, it can be customized to the domain context (each domain can have its own /txt, instead of having to do txt-com txt-org, etc.)
And because there's a fallback to the main domain or first entry or whatever, it's backwards compatible.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hey! I wanted to suggest an option for domain specific vanity urls (url shortener).
What does this mean? Pretty simple!
I think I'm not the only person using zipline with multiple domains and the support for it is good so far. But one awesome feature is missing: having an option to select which shortened url corresponds with which domain.
While creating a shortened url and giving it it's own vanity path, it would be awesome if we could also choose for which domain it corresponds (by default it should probably be the main or all)
Let's create a simple scenario everyone understands:
You own 3 domains, for each domain you have your own social media accounts or whatever but for the sake we use a txt file.
2 configured, one not.
example.com/txt -> example.com.txt
example.org/txt -> example.org.txt
Accessing com goes to com.txt, org to org.txt and accessing example.net/txt goes to the main one (let's say com.txt)
This way no one would need multiple instances just for the shortener or something, it can be customized to the domain context (each domain can have its own /txt, instead of having to do txt-com txt-org, etc.)
And because there's a fallback to the main domain or first entry or whatever, it's backwards compatible.
If you need more information, feel free to ask!
Beta Was this translation helpful? Give feedback.
All reactions