using ${project.machine_name}.docksal requires extra configuration by the user and the project machine name may not always match unless changed for local.blt.yml.
using ${env.VIRTUAL_HOST} will always read the environment variable of the already set VIRTUAL_HOST so that no additional config changes are needed. This is handing when you have to clone multiple instances of the same code base to test different branches simultaneously. It is also the recommended configuration in the Docksal and BLT blog post.
using
${project.machine_name}.docksalrequires extra configuration by the user and the project machine name may not always match unless changed for local.blt.yml.using
${env.VIRTUAL_HOST}will always read the environment variable of the already set VIRTUAL_HOST so that no additional config changes are needed. This is handing when you have to clone multiple instances of the same code base to test different branches simultaneously. It is also the recommended configuration in the Docksal and BLT blog post.