Commit 37b8c91a authored by Martyn Bissett's avatar Martyn Bissett

Update readme

parent 5bbcc4f9
......@@ -7,7 +7,7 @@ This is a vagrant for Wordpress projects
Firstly, ensure you have Vagrant installed, then:
git clone myproject
git clone myproject
cd myproject
cp Vagrantfile.example Vagrantfile
......@@ -41,36 +41,6 @@ This new IP address must match the IP address in /etc/hosts.
Also, if changing the domain, find instances of blog.vagrant in file
and change those to the new domain if that has changed too.
### Seeding database on vagrant up
Insert posts, pages, categories etc each time so the blog has content to work with
even if just in development.
This script will install wp-cli so we can install and setup our new installation
from the command line. This is also a really useful tool when we `vagrant ssh`.
Ensure these are placed at the end of the shell script:
Edit this line with your own user/pw/email for the admin user
# edit this line...
wp core install --url='<Blog URL>' --title='<Blog name>' --admin_user=<Admin user> --admin_password=<Admin user> --admin_email=<Admin email> --skip-email
Add some new lines to create posts/categories for testing in dev. These will be
created on a new vagrant up:
# Create posts
wp post create ./lipsum.txt --post_title='Keep calm this summer' --post_status=publish
# Create category
wp term create category "News" --description="News"
## Run vagrant
Now that and Vagrantfile are ready, start up the vagrant instance:
......@@ -81,8 +51,3 @@ vagrant up
It should now be possible to view the new blog in the browser with the domain used.
This will be http://blog.vagrant if unchanged.
## What now?
Unless you've change the `wp install` command in provision, your can login to wp-admin
with supervisor/strongpassword. Choose/download a theme, create menus, create posts etc
Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment