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
Installation on MODX Cloud - Anyone got it running? #107
Comments
If you haven't added Gitify to your path, then sometimes you need to user ./Gitify rather than Gitify to execute it. Have you tried that? |
yes, I get the following -ash: ./Gitify not found |
After chatting with the lovely Elizabeth, this is an environment specific issue on the particular Cloud instance you're using. The workaround is to edit the Gitify file, and to change the first line to This probably isn't an issue on the regular cloud servers. |
On a regular cloud instance, - the Amsterdam server I also needed to make this edit to the Gitify file |
So I got Gitify running on MODX Cloud except when I type in Gitify --help, I get the following error: |
Also instead of running composer install, I needed to run it this way $ php composer.phar install |
and when I use Gitify build, I get the following error: |
It turns out it was a cloud problem. I have create the following path for people to follow in case they wish to run Gitify on the cloud:
|
Thanks for the steps @sonicpunk! There's a typo in step 8: |
Thanks @ajilderda I edited my comment above |
The same steps as above, but a bit easier to copy paste for us lazy people. Ssh-login to your MODX Cloud instance:
change first line from
add
|
UPDATE: The following is no longer necessary and will break Gitify (at least it did on my cloud instance)
Seems to work fine with the first line left as is |
I went through the steps, installed Gitify, Composer, ran the composer install script... changed CHMOD.
From within my Gitify folder, the terminal tells me that Gitify is not found.
Here is my file structure:
Anyone have a tip?
The text was updated successfully, but these errors were encountered: