Vagrant - Migrate migrations and load initial data about bakerydemo HOT 6 CLOSED

Also, just an FYI, the load_initial_data currently only loads bakerydemo.json. At the moment, that only provides 1 superuser and no other content.

from bakerydemo.

There's lots of work to do on initial data loading - I'll take care of that. If anything special has to be done for vagrant data loading, please wait until I've got it working for the standard instructions.

from bakerydemo.

I think it would be better to remove these from provision.sh and make the user do them after provisioning. It keeps things consistent with the non-Vagrant instructions.

from bakerydemo.

Yes there's something to be said for making that consistent. Would your thinking be then that requirements would also be installed manually by the user rather than the provisioning shell file?

One bonus advantage would be that the user would never have difficulties if they hit the failed to mount folders vagrant problem that can sometimes happen since

from bakerydemo.

Interesting. The provision script does create the database....it just creates it in the wrong place.

If you vagrant ssh and poke around after a vagrant up, the bakerydemodb file is located at:

/home/vagrant

It needs to be created in /vagrant

With regard to moving the commands to manual steps, I would argue that we fix the issue at hand and automate as much as possible via the Vagrant path. The demo serves two different audiences. Developers are more than happy to manually execute commands, but this is also a very useful tool for non-developers that can be spun up to showcase Wagtail to potential stakeholders. For that audience, automation is key and removing the potential for human error will allow for a broader audience to come to the table.

from bakerydemo.

Closing this, as the only remaining work is load_initial_data which is handled via #10

from bakerydemo.