Using a custom domain

[LaCollision]

Hi everybody,

Hope you're all good 🤗

 

I'm calling for help for a problem that could open new horizons ^^

I have developed an app that allows members to create their own mini-website (it is something like the Invision Blog app).

One of the main request from my members is the ability to use their own custom domain name to be used on their mini-website.

For instance, instead of having their website homepage like:

https://www.myinvisioninstallation.com/website/{title}-{id}

… it would be:

https://www.the-member-domain-name.com

… pointing to the Invision installation.

It's not such an easy task with Invision, and I'm a bit lost on this one. So:

• Where would you start to enable such a feature?
• What kind of developments/hooks should be done?

I know it's a lot of work, but I'm just asking for the global picture, or if you would have any ideas on where to start.

 

Thank you very much! 🍻

[Adriano Faria]

I can be wrong but this is a domain stuff and will require redirects at server level. You can’t do that with only coding something in your app.

[LaCollision]

1 minute ago, Adriano Faria said:

I can be wrong but this is a domain stuff and will require redirects at server level. You can’t do that with only coding something in your app.

 

Hi,

Yes, the first step would be a custom DNS entry to redirect the member domain to the Invision installation.

But once this is done, the Invision installation must be able to work on a different domain (other than the 'base_url' constant defined in conf_global.php)… and that's where I call for help 🚨 😅

 

[opentype]

The IPS license prohibits this. You can only have one domain per license.

[LaCollision]

3 minutes ago, opentype said:

The IPS license prohibits this. You can only have one domain per license.

Hi,

The member custom domain name would be only used on just a few public pages from my 3rd-party app… so I'm not sure this would apply.

The whole Invision installation would only run on one domain.

[opentype]

Feel free to open a ticket and ask. But I’m very sure it will apply. You want to use one installation to provide a multi-domain service for your users (i.e. third-parties). That’s exactly what these kind of limitations are for. 

[bfarber]

In terms of "how" to do this, you would need to add some hooks on the Dispatcher code to prevent the redirect to the "correct" URL in this case.