Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: This does not seem to be a WordPress install #1

Closed
robfeldmann opened this issue Apr 21, 2014 · 2 comments
Closed

Error: This does not seem to be a WordPress install #1

robfeldmann opened this issue Apr 21, 2014 · 2 comments

Comments

@robfeldmann
Copy link

I'm experimenting with bedrock-ansible and I'm getting the following error. Seems it's not properly downloading Wordpress when it detects that it hasn't been installed yet. I'm not sure what the best way to address this is?

TASK: [wordpress-sites | WP installed?] *************************************** 
failed: [default] => (item={'site_install': True, 'admin_user': 'admin', 'site_name': 'gal-aa.dev', 'user': 'vagrant', 'multisite': {'enabled': False}, 'group': 'www-data', 'site_title': 'GaL-AA', 'admin_password': 'admin', 'env': {'wp_env': 'development', 'db_user': 'galaa_dbuser', 'db_password': 'galaa_dbpassword', 'wp_siteurl': 'http://gal-aa.dev/wp', 'db_name': 'galaa_dev', 'wp_home': 'http://gal-aa.dev'}, 'site_hosts': ['192.168.50.5', 'gal-aa.dev'], 'admin_email': '[email protected]'}) => {"changed": true, "cmd": ["wp", "core", "is-installed", "--allow-root"], "delta": "0:00:00.269877", "end": "2014-04-21 10:15:14.034539", "item": {"admin_email": "[email protected]", "admin_password": "admin", "admin_user": "admin", "env": {"db_name": "galaa_dev", "db_password": "galaa_dbpassword", "db_user": "galaa_dbuser", "wp_env": "development", "wp_home": "http://gal-aa.dev", "wp_siteurl": "http://gal-aa.dev/wp"}, "group": "www-data", "multisite": {"enabled": false}, "site_hosts": ["192.168.50.5", "gal-aa.dev"], "site_install": true, "site_name": "gal-aa.dev", "site_title": "GaL-AA", "user": "vagrant"}, "rc": 1, "start": "2014-04-21 10:15:13.764662"}
stderr: Error: This does not seem to be a WordPress install.
Pass --path=`path/to/wordpress` or run `wp core download`.
...ignoring

TASK: [wordpress-sites | Install WP] ****************************************** 
failed: [default] => (item={'item': {'site_install': True, 'admin_user': 'admin', 'site_name': 'gal-aa.dev', 'user': 'vagrant', 'multisite': {'enabled': False}, 'group': 'www-data', 'site_title': 'GaL-AA', 'admin_password': 'admin', 'env': {'wp_env': 'development', 'db_user': 'galaa_dbuser', 'db_password': 'galaa_dbpassword', 'wp_siteurl': 'http://gal-aa.dev/wp', 'db_name': 'galaa_dev', 'wp_home': 'http://gal-aa.dev'}, 'site_hosts': ['192.168.50.5', 'gal-aa.dev'], 'admin_email': '[email protected]'}, u'delta': u'0:00:00.269877', u'cmd': [u'wp', u'core', u'is-installed', u'--allow-root'], u'end': u'2014-04-21 10:15:14.034539', u'stderr': u'Error: This does not seem to be a WordPress install.\nPass --path=`path/to/wordpress` or run `wp core download`.', u'stdout': u'', 'invocation': {'module_name': 'command', 'module_args': u'wp core is-installed --allow-root chdir=/var/www/gal-aa.dev/current/'}, u'changed': True, u'rc': 1, u'start': u'2014-04-21 10:15:13.764662'}) => {"changed": true, "cmd": ["wp", "core", "install", "--allow-root", "--url=http://gal-aa.dev", "--title=GaL-AA", "--admin_user=admin", "--admin_password=admin", "[email protected]"], "delta": "0:00:00.242223", "end": "2014-04-21 10:15:14.824123", "item": {"changed": true, "cmd": ["wp", "core", "is-installed", "--allow-root"], "delta": "0:00:00.269877", "end": "2014-04-21 10:15:14.034539", "invocation": {"module_args": "wp core is-installed --allow-root chdir=/var/www/gal-aa.dev/current/", "module_name": "command"}, "item": {"admin_email": "[email protected]", "admin_password": "admin", "admin_user": "admin", "env": {"db_name": "galaa_dev", "db_password": "galaa_dbpassword", "db_user": "galaa_dbuser", "wp_env": "development", "wp_home": "http://gal-aa.dev", "wp_siteurl": "http://gal-aa.dev/wp"}, "group": "www-data", "multisite": {"enabled": false}, "site_hosts": ["192.168.50.5", "gal-aa.dev"], "site_install": true, "site_name": "gal-aa.dev", "site_title": "GaL-AA", "user": "vagrant"}, "rc": 1, "start": "2014-04-21 10:15:13.764662", "stderr": "Error: This does not seem to be a WordPress install.\nPass --path=`path/to/wordpress` or run `wp core download`.", "stdout": ""}, "rc": 1, "start": "2014-04-21 10:15:14.581900"}
stderr: Error: This does not seem to be a WordPress install.
Pass --path=`path/to/wordpress` or run `wp core download`.

FATAL: all hosts have already failed -- aborting

PLAY RECAP ******************************************************************** 
                     to retry, use: --limit @/Users/Rob/site.retry

default                    : ok=46   changed=3    unreachable=0    failed=1 
@swalkinshaw
Copy link
Member

This playbook isn't designed to download WP. It's meant to work with an existing Bedrock-based project/repo that already has it. For a dev environment this means having your local project synced through Vagrant. See the example synced_folder in the Vagrantfile.

For production environment, right now the best way is to set site_install to false, and then somehow deploy your site to the server. Bedrock comes with Capistrano by default which this playbook works with. Once the files are on the server, you can them manually install if you need to. Or import a database.

Some of this process needs to be improved but it will always expect you to have a project/repo from the start.

@robfeldmann
Copy link
Author

I see. Somehow I thought that the playbook would allow me to create/provision a new Bedrock-based Wordpress project from scratch. This makes sense though.

Thanks for the quick response!

On Apr 21, 2014, at 9:25 AM, Scott Walkinshaw [email protected] wrote:

This playbook isn't designed to download WP. It's meant to work with an existing Bedrock-based project/repo that already has it. For a dev environment this means having your local project synced through Vagrant. See the example synced_folder in the Vagrantfile.

For production environment, right now the best way is to set site_install to false, and then somehow deploy your site to the server. Bedrock comes with Capistrano by default which this playbook works with. Once the files are on the server, you can them manually install if you need to. Or import a database.

Some of this process needs to be improved but it will always expect you to have a project/repo from the start.


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants