Setup.php vs `bin/grav new-project`


I’m aware that setup.php can be used to guide a visitor to the right user/sites/$environment, but what about bin/grav new-project? It seems to symlink the Grav core files and create the user dependent dirs such as /backup, /user and /logs. To me that could be used to create Apache vhost dirs from a single Grav core instance. That way you only need to update a single instance, if I’m not mistaken.

So what’s the general best practice to maintain a single Grav core instance while hosting multiple Grav websites with different templates and plugins?

Anyone, please? If someone could share his/her experience with this and tell me what’s best, that would be greatly appreciated!