Best practices for custom url/domains

[Pierre-Lannoy]

Hello all!
I plan to deploy fusio as follow:

• developper portal => example.com
• api => api.example.com
• app "some-app" => some-app.example.com

Do you have some recommendations / best practices / guidelines to do that? Thanks ☺️

[chriskapp]

Hi @Pierre-Lannoy so we have recently added a Domains-Chapter s. https://github.com/apioo/fusio#domains to our readme. In general I would recommend to create an api.example.com for the Fusio API and an developer.example.com for the developer app, since those sub-domains are pretty widely used. Regarding the other apps there is currently no real standard, but I would recommend to place at example.com a product website which only explains your product and then links to the API and developer portal. Since you most likely need some good SEO for your product and our developer portal is an angular app which is not the best solution for SEO content.

[Pierre-Lannoy]

Thanks for your answer @chriskapp 👍🏼
Regarding the "main" domain, SEO is not really my concern: this dev portal will be open to all my clients (for some endpoints) and for everybody who want to use it for all other endpoints. And visits will be driven from my main website (hosterra.eu). So, not really a big deal… Nevertheless, thanks for you inputs which reinforces my idea of "breaking out" features in subdomains (and thanks for the documentation I had missed 😊)
From a technical point of view, what is the best approach?

• as many installs as there are sub-domains;
• a single install with subdomains roots pointing at the right dir;
• other way…