Issue with wp core install location about wp-deploy

[oxocode]

Uh oh...may want to remove / change the user credentials from the log above...

[chasefarthing]

yeah those aren't live / not the ones I plan on using. Still not a bad idea.

[aaronthomas]

Looks like there's something missing from the git repo your deploying from.

My first guess would be that the WordPress submodule doesn't exist in your repo, but as you mentioned the wordpress subfolder exists in your release so perhaps that's not the case.

Can you confirm that this file exists in the root of your repo, alongside the WP submodule?

It would also help to see file structure of your repo to make sure it's correct. Is this a public repo?

[chasefarthing]

The index file is there and matches yours. Here's what the files looks like on the server after the setup command:

It's not a public repo but here's what the file structure looks like:

If it'd help I could delete the password/login info and create a new public repo.
Thanks again for looking at this.

[aaronthomas]

Hmm, everything looks fine there to me.

Can you confirm that the wordpress folder in your release on the server is populated with the WP core files? Perhaps there was an issue cloning the submodule to your server.

It may also be worth running the wp:setup:remote task again, and double checking there were no other errors earlier in the log before this one.

Have you also tried to set up a local environment with wp:setup:local? It could be useful to see if that succeeds without problems.

[toby-griffiths]

I'm having a similar problem, and the /wordpress/ directory appears to be missing from my /releases/20140609141657 directory

[toby-griffiths]

Now I've re-run bash config/prepare.sh & pushed this to my repo, my /current/ directory now contains the /wordpress/ directory, but am still getting the same error.

[chasefarthing]

All the wordpress files are on the server in the release folder. When I run wp:setup:local It works just fine. It installs WP and I can log into the admin page.

Could it be where I'm deploying to?

I'm deploying just outside of my web root (html), and then symlinking it to the "current" folder. I'm guessing that's not the case if I can manually install wp while I'm in the wordpress folder in releases.

I feel like something isn't pointing the install instructions to the right folder.

[chasefarthing]

I tried this setup on a different server and am not getting this errors. Might have been acting weird on media temples gs hosting.

[sansgil]

I also seem to be getting this same error:

Error: This does not seem to be a WordPress install.
Pass --path=path/to/wordpress or run wp core download.

When trying to push my local db changes to my dev server on dreamhost. All the info in wp-config.php seems to be correct. The file structure on the server also looks to be correct based upon the comments above.

Any ideas why this isn't pushing the local db to the remote dev server?

[beehive]$ pwd
/home/mountyeti/dev.mountyeti.com/current
[beehive]$ ls -la
total 44
drwxr-xr-x 6 mountyeti pg8130016 4096 Oct 25 04:28 .
drwxr-xr-x 3 mountyeti pg8130016 35 Oct 25 04:27 ..
lrwxrwxrwx 1 mountyeti pg8130016 50 Oct 25 04:28 .htaccess -> /home/mountyeti/dev.mountyeti.com/shared/.htaccess
-rw-r--r-- 1 mountyeti pg8130016 493 Oct 25 04:23 Capfile
-rw-r--r-- 1 mountyeti pg8130016 84 Oct 25 04:23 Gemfile
-rw-r--r-- 1 mountyeti pg8130016 541 Oct 25 04:23 Gemfile.lock
-rw-r--r-- 1 mountyeti pg8130016 1085 Oct 25 04:23 LICENSE.md
drwxr-xr-x 4 mountyeti pg8130016 4096 Oct 25 04:23 config
drwxr-xr-x 5 mountyeti pg8130016 83 Oct 25 04:28 content
-rw-r--r-- 1 mountyeti pg8130016 405 Oct 25 04:23 index.php
drwxr-xr-x 3 mountyeti pg8130016 31 Oct 25 04:23 lib
-rw-r--r-- 1 mountyeti pg8130016 7683 Oct 25 04:23 readme.md
-rw-r--r-- 1 mountyeti pg8130016 25 Oct 25 04:28 robots.txt
drwxr-xr-x 5 mountyeti pg8130016 4096 Oct 25 04:26 wordpress
lrwxrwxrwx 1 mountyeti pg8130016 54 Oct 25 04:28 wp-config.php -> /home/mountyeti/dev.mountyeti.com/shared/wp-config.php
[beehive]$ ls -la wordpress/
total 192
drwxr-xr-x 5 mountyeti pg8130016 4096 Oct 25 04:26 .
drwxr-xr-x 6 mountyeti pg8130016 4096 Oct 25 04:28 ..
-rw-r--r-- 1 mountyeti pg8130016 418 Oct 25 04:26 index.php
-rw-r--r-- 1 mountyeti pg8130016 19930 Oct 25 04:26 license.txt
-rw-r--r-- 1 mountyeti pg8130016 7192 Oct 25 04:26 readme.html
-rw-r--r-- 1 mountyeti pg8130016 4951 Oct 25 04:26 wp-activate.php
drwxr-xr-x 9 mountyeti pg8130016 4096 Oct 25 04:26 wp-admin
-rw-r--r-- 1 mountyeti pg8130016 271 Oct 25 04:26 wp-blog-header.php
-rw-r--r-- 1 mountyeti pg8130016 4946 Oct 25 04:26 wp-comments-post.php
-rw-r--r-- 1 mountyeti pg8130016 2746 Oct 25 04:26 wp-config-sample.php
drwxr-xr-x 4 mountyeti pg8130016 65 Oct 25 04:26 wp-content
-rw-r--r-- 1 mountyeti pg8130016 2956 Oct 25 04:26 wp-cron.php
drwxr-xr-x 12 mountyeti pg8130016 8192 Oct 25 04:26 wp-includes
-rw-r--r-- 1 mountyeti pg8130016 2380 Oct 25 04:26 wp-links-opml.php
-rw-r--r-- 1 mountyeti pg8130016 2714 Oct 25 04:26 wp-load.php
-rw-r--r-- 1 mountyeti pg8130016 33043 Oct 25 04:26 wp-login.php
-rw-r--r-- 1 mountyeti pg8130016 8252 Oct 25 04:26 wp-mail.php
-rw-r--r-- 1 mountyeti pg8130016 11115 Oct 25 04:26 wp-settings.php
-rw-r--r-- 1 mountyeti pg8130016 26256 Oct 25 04:26 wp-signup.php
-rw-r--r-- 1 mountyeti pg8130016 4026 Oct 25 04:26 wp-trackback.php
-rw-r--r-- 1 mountyeti pg8130016 3032 Oct 25 04:26 xmlrpc.php