Why only 2 domains
Hey, I have a question about the domains support. Why is there only 2 domains support for the hobby account? I need 3 domains for my personal projects. Is there any way to get an extra domain without upgrading to a higher plan? I really like your service but I don't need to upgrade to Pro.
19 Replies
Project ID:
65831437-893e-408b-bdc2-09bd97ce8244
65831437-893e-408b-bdc2-09bd97ce8244
It really wont do to just 2
Why is there only 2 domains support for the hobby account?the team has determined that 2 custom domains are going to be sufficient for most hobby use cases
Is there any way to get an extra domain without upgrading to a higher plan?there isnt, sorry but with that said, the team is always open to the possibility of change, so please do share your hobby use case for 3 domains on a service!
No, I think I will just return to DO. Thank you!
oh okay?
No problems, but it seems to be too much for an additional domain. I was surprised because I couldn't find any information in the documentation, and I need the extra domain now anyway.
But thank you
the documentation has not yet been updated to reflect the 2 domain limitation on the hobby plan
Yes, please update it. I lost a couple of hours because of that
i will talk to the right people to make it happen!
Ohh, and just for you to know, that limitation is super weird
honestly unless i knew your use case, i unfortunately cant share that sentiment
I've got this website called pythoncheatsheet.org, and I'm just putting the finishing touches on an app to send newsletters to 10k+ subscribers because the current newsletter apps out there are too expensive. I need three domains : one for the API, another for the main publication website, and the last one for the URL shortener, so I can track the clicks.
all those features are all built into a single service?
yes
well, pythoncheatsheet lives on his own
does the app do internal host based routing?
no
could you split the functionality into multiple railway services?
It's just the API to connect to the dashboard (Vercel), the publication site, which is a static page (Django template), and an internal app that uses another domain for to shorten the URLs. It's super simple, so it does not need to be overengineered.
I already have 3: the api, the worker and the beat
well, I just deleted them lol
I think I will keep the database and redis there for now
sounds good!