Closed mootpt closed 8 years ago
Thanks for reporting this @mootpt
It's something that we're considering adding, both from the AppCatalyst standpoint (starting up the daemon on boot, having a menubar helper to start/stop the daemon) and from the Vagrant provider (adding a do you want to start the daemon? [y/n]
prompt).
Thanks @frapposelli.
It is apparently unvagranty to prompt the user for any input on the provisioning of a machine. If the user is wanting to use the appcatalyst stack it makes sense to do one of two things:
This issue should have been closed by #20, oops.
Appcatalyst provider does not work out of the box and requires the appcatalyst-daemon to be started before vagrant will function properly. This behavior is unexpected for most, as the existing VMware providers don't require a separate daemon to be running for
vagrant up
to function as expected:Ideally, the daemon should be handled by the provider and/or this requirement should be documented.