Various enhancements, including fixing root permissioning, allowing debugging using a local Chrome instance within the VM, spacers between items in the catalog and printing a (currently fake) list of author names along with the book titles. Will move to non-fake names once these are available in the db.
@ojongerius - I'm not sure there's much value in changing to a grep. Since this is run during provisioning, these are the possibilities:
initial "vagrant up": the file won't exist as gradle has never run before in this VM, and will be created
later "vagrant reload":
The file already exists (with or without manual changes by the user), so no action is taken
The file was deleted somehow, and is recreated. If the user did this as a way to disable the gradle daemon, they can instead change their config to "false" to prevent this from happening.
Various enhancements, including fixing root permissioning, allowing debugging using a local Chrome instance within the VM, spacers between items in the catalog and printing a (currently fake) list of author names along with the book titles. Will move to non-fake names once these are available in the db.