For DynaBlogger I have the main domain www.dynablogger.com for the landing page, app.dynablogger.com for the actual app, and for user sites I am using a different domain instead - dynablogger.net - because that's usually a good practice for security reasons when your users can create content on your platform. Each site gets a subdomain of that domain (although users can add custom domains too).
For DynaBlogger I have the main domain www.dynablogger.com for the landing page, app.dynablogger.com for the actual app, and for user sites I am using a different domain instead - dynablogger.net - because that's usually a good practice for security reasons when your users can create content on your platform. Each site gets a subdomain of that domain (although users can add custom domains too).
Exactly the same practice that I use!
That's great!
I don't think I need different domains for each user (or tenant) in this app. Actually glad, didn't want to have to deal with SSL and custom domains 😂
Another Laravel user I see :) Sub-domain routing is great. Doing a similar thing with my apps.
🏄♂️Laravel 4 Life 😀
Today I split the SaaS application across some subdomains.
The landing page will be hosted at podcastsping.com
The application will be hosted at app.podcasting.com
The web hooks handling will be hosted at hooks.podcastping.com
Made use of Laravel's sub-domain routing feature to make this work.