alexc7018 / vvv-site-wizard Goto Github PK

So the admin 404s, sub pages 404.

When I ran this the first time it correctly generated the site and the databases required. However, when I went to the .dev link it was giving me the standard vvv.dev information. After some digging I discovered the the site.conf file was generated but it was empty. Could this be a permissions issue on my side or has anyone else run into this issue?

Sorry, I'm certain this is a config issue on my end and not a fault of this tool, but I'm having issues getting the VVV Site Wizard to do everything for me. When I run it, it fails both of its calls to vagrant on my system.

New VVV setup starting for site 'testsite'
./vvv: line 334: vagrant: command not found
Creating site directory, wp-cli.yml, and vvv-init.sh file... Done.
Adding testsite.dev to new vvv-hosts file... Done.
Creating nginx-config/sites/testsite.conf... Done.
Running vagrant up --provision...
./vvv: line 395: vagrant: command not found

I've tried running the script from a nested directory ( /vagrant/www/vvv-site-wizard/ ) as well as the base of my vagrant install ( /vagrant ).

After running the script, I'm able to manually "vagrant halt" and then "vagrant up --provision" from my DOS prompt (I'm running this on a windows machine, but executing vvv from inside an ssh terminal to the VM) so that I can see the site, and everything works as it should. But I would love to be able to have the site wizard do this for me like it's trying to.

Any advice would be extremely welcome. Sorry for the n00b-ness :) Thanks!!

Sorry for the junk-issue... but good golly, woman. Killer tool!

HI,

Just started getting a 'nginx 403 Forbidden' on newly created sites, also the database doesn't get populated, any troubleshooting tips for this.

The previously created sites still remain accessible, no custom configuration been applied to box.

Thanks

Howdy,

I'm currently using VVV in place of MAMP; i.e. I have one instance that I use to develop a number of client's sites. This is working fine, but the whole process of booting/halting the virtual machine is getting kinda long with the number of sites I have in there; especially the sites with very large databases.

I'm wondering if there is a way I can disable sites that I only work with now and then, so that they don't load up on the vagrant up command?

Cheers,
Phil

Just used your script, that looks perfect for what i want to do, but nginx threw a "403 Forbidden" when i typed the address.dev in the address bar.

Any idea why?

ubuntu trusty64 box
vagrant 1.7.2
wordpress 4.1.1

Sometimes when I install a new site, WordPress doesn't install into the htdocs, it just leaves it empty. I can't figure out why this would happen.

Hi

Please set the image_proxy to n as default so it doesn't prompt or remove the i option

Paul

When i create a new site from the vagrant root folder with command "vvv-site-wizard/vvv", all the existing sites are being updated to the latest wordpress version.

Is this default behaviour? Is it possible to create a new site without having the other sites updated as well?

I see that you explicitily state that the site teardown does not remove the database. But why not? I would really like it to, or at least have a flag to send or something that does.

Yes I can go into phpmyadmin and drop the database, but it would be nice if I could simply do it right from the teardown wizard.

Is there a reason this is not the case?

When creating new WordPress site, it would be better to use latest stable version instead of trunk.

I'm a bit confused of how to get this installed. When I run $PATH it returns this:

-bash: /Users/realph/.node/bin:/usr/local/bin:/Users/realph/.rbenv/shims:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin: No such file or directory

Do I just download the repo, and dump the vvv file into this folder /Users/realph/.node/bin?

Any help with this is appreciated. Thanks in advance!

The last time I used this script I had two sites to scaffold. This time I have 5.

It would be nice if the script could let me tell it all the sites I want before it does the vagrant halt, provision, up cycle.

Hi, were having some difficulties on one of our machines at work when running site-wizaed. It appears to run fine and creates the directory on our vv roots but the htdcos directory is empty and there is no db created. We have tried placing vvv in the path environment variable (i.e /bin) and in the vvv root directory. the error message that appears during install is :

==> default: PHP Fatal error: Uncaught exception 'UnexpectedValueException' with message 'phar tar error: "/home/vagrant/.wp-cli/cache/core/en_US-4.0.1.tar.gz" already exists as a regular phar and must be deleted from disk prior to creating as a tar-based phar' in /srv/www/wp-cli/php/commands/core.php:181
==> default: Stack trace:
==> default: #0 /srv/www/wp-cli/php/commands/core.php(181): PharData->__construct('/home/vagrant/....')
==> default: #1 /srv/www/wp-cli/php/commands/core.php(154): Core_Command::_extract('/home/vagrant/....', '/srv/www/test/h...')
==> default: #2 [internal function]: Core_Command->download(Array, Array)
==> default: #3 /srv/www/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(52): call_user_func(Array, Array, Array)
==> default: #4 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher{closure}(Array, Array)
==> default: #5 /srv/www/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(295): call_user_func(Object(Closure), Array, Array)
==> default: #6 /srv/www/wp-cli/php/WP_CLI/Runner.php(304): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array)
==> default: #7 /srv/www/wp-cli/php/WP_CLI/Runner.php(311): WP_CLI\ in /srv/www/wp-cli/php/commands/core.php on line 181
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=path/to/wordpress or run wp core download.

Were all a bit new to vvv here so forgive our 'noubness', any help would be greatly appreciated, cheers

Would be nice to have a switch and nginx config to support installing WordPress in a subdirectory ala WP Skeleton: https://github.com/markjaquith/WordPress-Skeleton

You can see an example of the subdirectory rules in HHVVVM: https://github.com/johnjamesjacoby/hhvvvm/blob/master/nginx-wp-subdirectory.conf-sample#L40

This is awesome, but I am having an issue in windows. If I edit the vvv file, what should the path read? Right now I have path=e:/vvv (which is my varying vagrants folder), it's not in vagrant-local. Or am I supposed to be using a folder on the vvv machine? Any help would be appreciated! Thanks!

Having trouble getting started with vvv-site-wizard. I'm getting this in the output from the --provision started after running the vvv-site-wizard script:

==> Creating database 'wswork' (if it does not exist)...
==> Installing WordPress (release version) in wswork/htdocs...
==> Warning: cURL error 7: Failed to connect to api.wordpress.org port 443: Connection timed out
==> Error: cURL error 7: Failed to connect to api.wordpress.org port 443: Connection timed out
==> Error: This does not seem to be a WordPress install.
==> Pass --path=path/to/wordpress or run wp core download.
==> Error: This does not seem to be a WordPress install.
==> Pass --path=path/to/wordpress or run wp core download.

and the directory /www/wswork contains:
htdocs
vvv-hosts
vvv-init.sh
wp-cli.yml

Here's the config info:
"New VVV Site Setup
Directory /Users/amallory/webdev/nhn/www/ already exists.
Name of new site directory: wsworkforce
Domain to use (leave blank for wsworkforce.dev):
WordPress version to install (leave blank for release version):
Load images from live site (y/n): n

About to perform the following:

• Halt Vagrant (if running)
• Create directory wswork in /Users/amallory/webdev/nhn/www
• Create files vvv-init.sh, wp-cli.yml, and vvv-hosts in directory wswork
• Create file wswork.conf in /Users/amallory/webdev/nhn/config/nginx-config/sites
• Run vagrant up --provision to initialize site

Provisioning Vagrant will do the following:

• Create database wswork
• Install WordPress (release version) in the htdocs directory
• Make the site visible at wsworkforce.dev

Continue (y/n)? y

New VVV setup starting for site wswork" ....

So it looks like things aren't getting processed when the provision is run? Any idea why?

This may be a silly question but its causing me some difficulties. Ive installed vvv-site wizard, everything seems to be running ok and i can run through the wp installation process easily with no errors. My problem is when i visit the domain that is generated by vvv - site wizard it takes me to the "Index of" screen, as if theres no index.php file inside the directory. All the Wordpress files have been downloaded, database has been created and the wp-cli.yml file is pointing to "path: htdocs". May be Im installing the wizard wrong.

Currently its in my vagrant root directory but i have also tried placing it inside my bin directory, as a colleague suggested it may help, but no joy.

Any help would be greatly appreciated.

The source code says

# When not called from the VVV root directory, the script will prompt the user
# for the path to VVV. To run this from any directory and skip that prompt,
# uncomment the following line and set it to the VVV root dir:
#path=/path/to/vvv/root

However, uncommenting that will create a new file change in git. Should there be a better way to configure this without changing the source? Perhaps an environment variable?

I have about 15 dev sites active in my VVV install now.

It would be nice if the vvv-site-wizard script could update vvv.dev so that it lists the sites it has created in there.

I guess part of the functionality is already built as you can run vvv and ask it to list the existing sites that way but an easily clickable html link would be better for quick development.

I have a space in my path to my vvv root. No matter how I type the path, I get an error. I've used quotes and/or forward slashes, neither of which work. What am I doing wrong?

for instance:
path="/Users/jacob/Desktop/Dropbox/Active Web Projects/vvv"
path=/Users/jacob/Desktop/Dropbox/Active\ Web\ Projects/vvv

when I throw vvv on my desktop, everything works:
path=/Users/jacob/Desktop/vvv

Thanks!

Hi!

Just wondering.. from my understanding the newer version of VVV has changed the way it creates/accesses mysql databases. Now it seems you need to write two lines in the vvv/database/init-custom.sql file for it to properly do a backup on each halt etc.

Have vvv-site-wizard been updated to accommodate for these changes? I.e. automatically adds the necessary lines for each new site / removes them for sites being deleted..

Thanks!

I have VVV working with hyper-v on windows 8.1 very well and I love the vvv-site-wizard, just have small issue with the setup that I need help with.

Its not copying WordPress into the htdocs folder and appears to be some permissions problem. Here is the errors I see.

==> default: http://gruntjs.com/getting-started
==> default: PHPMyAdmin already installed.
==> default: Creating database 'dha' (if it does not exist)...
==> default: Installing WordPress 3.9.1 in dha/htdocs...
==> default: Downloading WordPress 3.9.1 (en_US)...
==> default: Using cached file '/home/vagrant/.wp-cli/cache/core/en_US-3.9.1.tar.gz'...
==> default: PHP Warning:  mkdir(): Permission denied in /srv/www/wp-cli/php/commands/core.php on line 116
==> default: PHP Warning:  mkdir(): No such file or directory in /srv/www/wp-cli/php/commands/core.php on line 116
==> default: PHP Warning:  mkdir(): No such file or directory in /srv/www/wp-cli/php/commands/core.php on line 116
==> default: PHP Warning:  mkdir(): No such file or directory in /srv/www/wp-cli/php/commands/core.php on line 116
==> default: PHP Warning:  copy(/srv/www/dha/htdocs//wp-content/plugins/akismet/_inc/akismet.js): failed to open stream: No such file or directory in /srv/www/wp-cli/php/commands/core.php on line 119
==> default: PHP Warning:  mkdir(): No such file or directory in /srv/www/wp-cli/php/commands/core.php on line 116
==> default: PHP Warning:  copy(/srv/www/dha/htdocs//wp-content/plugins/akismet/_inc/img/logo-full-2x.png): failed to open stream: No such file or directory in /srv/www/wp-cli/php/commands/core.php on
 line 119
==> default: PHP Warning:  copy(/srv/www/dha/htdocs//wp-content/plugins/akismet/_inc/akismet.css): failed to open stream: No such file or directory in /srv/www/wp-cli/php/commands/core.php on line 119

there is the permission denied with the mkdir request from wp_cli and then issue with copy directory. I am uncertain if there is a problem with the addition of an extran /. the copy command appears to have 1 to many / after htdocs I think, I may be wrong.

==> default: PHP Warning:  copy(/srv/www/dha/htdocs//wp-content/plugins/akismet/_inc/akismet.css): failed to open stream: No such file or directory in /srv/www/wp-cli/php/commands/core.php on line 119

Everything is works great. At the moment I just need to drop the WordPress files into htdocs and it's rock-n-roll. I thought it would be important to advise this is happening and see if I could get some direction as to where this error results from.

Thanks again

Hi

As you test for ./htdocs folder this returns true if we have mapped a folder in the it is better to test for ./htdocs/wp-admin

Hi! I would like to submit a formula to install this via Homebrew, however they require that the formula be installing a tagged release, not simply HEAD (see https://github.com/Homebrew/homebrew/wiki/Acceptable-Formulae#stable-versions). Can you tag a 1.0 release? Thanks!

As an enhancement, the installation instructions could alternatively mention:

curl -s https://raw.githubusercontent.com/aliso/vvv-site-wizard/develop/vvv > /usr/local/bin/vvv; chmod +x /usr/local/bin/vvv

This moves vvv into the local bin with permission to be executed from anywhere.

During script, encountered this error:

==> default: Updating to version 4.0 (en_US)...
==> default: Success: WordPress is at the latest version.
==> default: Success: WordPress database upgraded successfully.
==> default: Creating database 'examplesite' (if it does not exist)...
==> default: Installing WordPress (release version) in examplesite/htdocs...
==> default: Downloading WordPress 4.0 (en_US)...
==> default: Using cached file '/root/.wp-cli/cache/core/en_US-4.0.tar.gz'...
==> default: 
==> default: Fatal error: Uncaught exception 'UnexpectedValueException' with message 'phar tar error: "/root/.wp-cli/cache/core/en_US-4.0.tar.gz" already exists as a regular phar and must be deleted from disk prior to creating as a tar-based phar' in /srv/www/wp-cli/php/commands/core.php:180
==> default: Stack trace:
==> default: #0 /srv/www/wp-cli/php/commands/core.php(180): PharData->__construct('/root/.wp-cli/c...')
==> default: #1 /srv/www/wp-cli/php/commands/core.php(153): Core_Command::_extract('/root/.wp-cli/c...', '/srv/www/exampl...')
==> default: #2 [internal function]: Core_Command->download(Array, Array)
==> default: #3 /srv/www/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(52): call_user_func(Array, Array, Array)
==> default: #4 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array)
==> default: #5 /srv/www/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(293): call_user_func(Object(Closure), Array, Array)
==> default: #6 /srv/www/wp-cli/php/WP_CLI/Runner.php(304): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array)
==> default: #7 /srv/www/wp-cli/php/WP_CLI/Runner.php(311): WP_CLI\Runner->ru in /srv/www/wp-cli/php/commands/core.php on line 180
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=`path/to/wordpress` or run `wp core download`.
==> default: Error: This does not seem to be a WordPress install.
==> default: Pass --path=`path/to/wordpress` or run `wp core download`.
==> default: /srv/www/examplesite`

Not surprisingly, the WP install never happened. I was able to get this back to working after logging into vagrant (vagrant ssh, sudo -i) changing dir to the hidden .wp-cli folder and removing the tar files within. Hope this helps someone else.

I pulled down a live site to work on locally, and selected Yes for using images from the production server.

A lot of the images still come up as 404. I realized that any image that was hardcoded into the site with the prefix "www." comes up 404. If there is no "www.", then it pulls from production fine. I even went in after the page loaded and, via chrome inspector, manually removed the "www." from one of the broken images, and then it immediately loaded the production image fine.

How can I fix this so that it loads from the production server for both the url not containing "www." but ALSO the url that does contain "www."?