edfullman1

Changed the permissions to the same as the rest of the wordpress install bitnami:daemon, but alas that’s not the answer. Getting the same error and the help screen still says false on permissions.

Do you get this any other time on AWS? Do I need to create one of these index.lock files manually?

Any other ideas?

The whoami you suggested retrieved “daemon”

What permission is lacking a group permission or something? The directory where the repo is located has write permissions set.

Any thoughts?

Some headway. I was able to use the ‘git pull’ from the command line. This seems to have the local at the right point now. When I went into Revisr it read the push, so the HTTPS seems to be working. That resolves the remote.

This is from the dashboard. “Successfully pushed 2 commits to origin/master.“

However, when I tried to do a commit from Revisr, I got an error that it can’t write to the local. This is the error.

There was an error committing the files. Make sure that your Git username and email is set, and that Revisr has write permissions to the “.git” directory.

I did a “git config –global” on the username and email, and it still gets the same error.

What do you think is wrong with the permissions to write?

I added: define( ‘REVISR_GIT_PATH’, ‘/usr/bin/git’ ); to the wp-config.php already. Then I restarted Apace. Do I need to do something to WordPress to get it to read the config change?

Hi,

I tried putting in the HTTPS version. It failed, but the error detail was different.

To https://[username}:[password]@github.com/[organization]/[directory]
! [rejected] HEAD -> master (non-fast-forward)
error: failed to push some refs to ‘https://[username}:[password]@github.com/[organization]/[directory]’
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: ‘git pull …’) before pushing again.
hint: See the ‘Note about fast-forwards’ in ‘git push –help’ for details.

I don’t think this fixed the SSH problem, and file permissions still reads as “false”.

Maybe it sheds some light on the problem for you.

Actually, I left out that I tried HTTPS first.

This is actually a Bitnami image on an AWS Instance. So I control the instance completely.

Here is a better link to our blog, where the issue actually occurs.