What are best practices in a dev environment for creating database tables and populating data during "vagrant up", also keeping in mind the need to re-run provisioning at times?
Right now I have used chef to install postgresql, create a user and database. The next step is creation of tables followed by population of tables from CSV. One idea I have is to create separate sql scripts for table creation and table population and call these from the vagrant bash provisioner. If I prefix the table creation scripts with "drop table" commands then running vagrant provision should restore things back to how they were, although it would be nice if I could have an option to skip the sql parts during certain provisions. Is this the way to go? Rhys -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
