• Resolved Adam Walter

    (@adamwalter)


    I’ve been using Git for a long time, so I’m comfortable with it. However, I’m having trouble getting the plugin setup. I am confident that I have everything setup correctly:

    • I have a stock WordPress installation in the root folder of my git repo
    • I have the repo synced to Github, and am able to do all git actions successfully via the command line, so my SSH key and authentication are working fine
    • If I make a change to a file, git is showing the changes like normal
    • Revisr is installed and my username and email address are configured

    But if I make any changes to tracked files, I’m not seeing any recent activity on the Revisr dashboard. I made a test commit anyways and didn’t get an error, but the commit isn’t registering in git and not showing up on Github. If I try a pull or push, I get:

    There was an error while pushing to the remote repository. The remote may be ahead of this repository or you are not authenticated.

    My repo is up to date and like I said, SSH auth is working fine on the command line. I tried using the https option, but no dice.

    I’m assuming something isn’t setup correctly! But installation instructions are a little vague. I’m running WP locally on MAMP. Could that be it?

    https://wordpress.org/plugins/revisr/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Expanded Fronts

    (@expandedfronts)

    Hello,

    Updated documentation is on the way and I’ll let you know as soon as that’s been posted. I’ll also be sure to test on MAMP to make sure there are no compatibility issues there and will push out updates as needed.

    Thanks for the feedback!

    Thread Starter Adam Walter

    (@adamwalter)

    It’s definitely not working on MAMP. I moved my site to my web server and everything appears to be working fine.

    Plugin Author Expanded Fronts

    (@expandedfronts)

    Hi Adam,

    Did some more testing on Mac OSX with MAMP and confirmed the issue is specific to MAMP. It appears that MAMP forces a different path for Git than the default path.

    So instead of the default path, in my case usr/bin/.., it was pushing through to a path specific to MAMP. See here and here for more information and some possible fixes.

    Thread Starter Adam Walter

    (@adamwalter)

    Okay, good to know. I will check that out!

    I had the same error message, and got it working eventually. I have a different server setup though (Rasbian/gninx/php/mysql). But some of the following might apply for others as well.

    • Make sure www-data (or the user your script is running under) has a SSH key (without password), and that it is added to your bitbucket/github account. ssh-keygen
    • Make sure that the .git directory in your repositories root folder has the correct permissions, as well as some of the files in it. The www-data user needs writing permissions. Note: the .git directory is hidden. Check its permissions with ls /var/www/.git -la. Set permissions recursively with chmod -R 770 /var/www/.git
    • Do an initial push to remote from the commandline, as www-data user. The first time ssh will say the rsa fingerprint of the remote server is unknown, and asks you to add it permanently.

    Out of curiosity, do you think you’ll be adding support for MAMP?

    Plugin Author Expanded Fronts

    (@expandedfronts)

    Hi Andrew,

    It’s something we’re looking into, although the issues with MAMP support are beyond simple plugin configuration and require making sure that the environment paths to Git are set correctly for MAMP.

    When we find a good solution that seems to work for everybody, we’ll update the plugin and/or documentation as necessary.

    Plugin Author Expanded Fronts

    (@expandedfronts)

    Hi All,

    You can make Revisr work with MAMP by opening the following file:
    /Applications/MAMP/Library/bin/envvars

    And commenting out the two lines so it looks like this:

    if test "x$DYLD_LIBRARY_PATH" != "x" ; then
      #DYLD_LIBRARY_PATH="/Applications/MAMP/Library/lib:$DYLD_LIBRARY_PATH"
    else
      #DYLD_LIBRARY_PATH="/Applications/MAMP/Library/lib"
    fi
    export DYLD_LIBRARY_PATH

    This will be included in the documentation today, so I’m marking this as resolved.

    Let me know if you run into any further issues. Thank you.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘More detailed installation documentation’ is closed to new replies.