In the project settings there’s an option to select a hosting type:
When this setting is changed on an existing project all setup targets are removed and you have to re-create them, except one default.
Regardless of this setting local and remote Docker targets can be created, even when the Custom Hosting Hosting type is selected.
Vice versa targets with other hosting types are possible when 'Docker Hosting` is selected.
It seems to me this setting is just meant to setup the first, default target automatically, but I am not sure. @Teodor might have the complete answer to this question I suppose?
The hosting settings determines your project structure. Recently we allowed to be able to change the hosting type for existing projects, so you can easily switch from no hosting, to firebase hosting for just static pages, to later Heroku for example when you need NodeJS.
So now it is possible to switch and all the needed settings are applied to your current project. So you are not limited to your initial project creation choice.
Indeed if you switch hosting, you will need to redefine your targets, as those are changed as well.
Okay, but do I understand correctly that this is only used for initial setup (of the first default target)?
So if a project has, besides the default local target, a local Docker target for development and a Heroku target for production, it doesn’t actually matter which hosting type is selected in the project settings. Is that correct?
