Updating Vagrant section to MAMP/WAMP/VVV #148
Conversation
Added a separate guide for MAMP setup
|
Files that need updates as a part of this PR |
|
|
||
| ## Setup a Largo Blueprint for VV | ||
|
|
||
| One useful feature of VV is that it allows you to create "blueprints" for site configurations. Below, we'll setup a basic blueprint for Largo sites. |
There was a problem hiding this comment.
Will we need to create new blueprints for each of the Largo umbrellas?
There was a problem hiding this comment.
I don't believe so - the general vv create command will walk through site setup options, where you can specify a mysql database and external repo to use for wp-content, which I think is probably the way to go.
We'll need to modify our bitbucket repo a bit so things match up better, but that should be about it.
|
I think this is just about ready for review - the VVV pieces should be all set, there's just a few other related things I noticed
|
| Run the following commands to initialize a new git repository and sync it with the largo-umbrella remote. This is similar to cloning a git repository, but lets us work with the files and folders we already have setup. | ||
| ``` | ||
| git init | ||
| git remote add origin git@bitbucket.org:rclations/largo-umbrella.git |
There was a problem hiding this comment.
This repo is not currently public; will we be making it public or merging it into the largoproject version?
There was a problem hiding this comment.
good catch - just updated with f407bcb
| 5. You may then see the message "Already Installed" because you already loaded the WordPress database in a previous step. | ||
|
|
||
| ## 13. Changing largoproject.wpengine.com to vagrant.dev. | ||
| ## 12. Changing largoproject.wpengine.com to vagrant.dev. |
There was a problem hiding this comment.
Should this section also include the wp method seen here?: https://github.com/INN/docs/blob/master/projects/largo/database-reload.md#4-replace-primary-wp_-tables-with-local-environment-urls
There was a problem hiding this comment.
yeah, definitely - I'll add that in
There was a problem hiding this comment.
updated in c9c02e3
Replacing search/replace instructions with those from https://github.com/INN/docs/blob/master/projects/largo/database-reload.md
| ------------ | ------------- | ||
| Name of new site directory: | largo-umbrella | ||
| Blueprint to use (leave blank for none or use largo): | *hit [Enter]* | ||
| Blueprint to use (leave blank for none or use largo): | *hit [Enter]* |
Changes
Why?
We needed a simpler option for new users to get started with development, without having to setup a custom Vagrant build. MAMP & WAMP offer a simple alternative, while VVV streamlines our existing Vagrant process for advanced users and takes care of a lot of the inherent bugs.
Benefits of VVV
In addition, by adopting standard tools widely used in the community, we grow our ability to attract new developers to contribute to our projects.
This would fix issues #41 & #47, by removing the functionality they address in favor of using VVV.
Related
INN/deploy-tools#48