The prompt to run the setup_wizard after generating a new Hobo 2.x application should include a note to the effect that the generated project is incomplete until the wizard is run. Only when the wizard is run does Hobo generate the critical (mandatory) asset files. If you DON'T run the wizard and launch your application, Hobo bails as soon as it tries to load taglibs/application.dryml which doesn't exist yet.
That's not a happy start to a new Hobo project.
Of course, the best solution would be to have the default assets created in the 'hobo new' stage, with prompts to overwrite when the setup_wizard is run.
The prompt to run the setup_wizard after generating a new Hobo 2.x application should include a note to the effect that the generated project is incomplete until the wizard is run. Only when the wizard is run does Hobo generate the critical (mandatory) asset files. If you DON'T run the wizard and launch your application, Hobo bails as soon as it tries to load taglibs/application.dryml which doesn't exist yet.
That's not a happy start to a new Hobo project.
Of course, the best solution would be to have the default assets created in the 'hobo new' stage, with prompts to overwrite when the setup_wizard is run.