-
Notifications
You must be signed in to change notification settings - Fork 16
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
Lots of issues - Not pushing most of the times #35
Comments
dir listing: forge@somewebsite-online:~/somewebsite.online$ ls -al /home/forge/somewebsite.online/
total 48
drwxrwxr-x 7 forge forge 4096 Feb 23 14:50 .
drwxr-xr-x 7 forge forge 4096 Feb 23 14:08 ..
-rw-r--r-- 1 forge forge 459 Feb 23 07:40 .env
drwxrwxr-x 8 forge forge 4096 Feb 23 15:20 .git
-rw-rw-r-- 1 forge forge 239 Feb 23 14:50 .gitignore
-rw-rw-r-- 1 forge forge 18 Feb 23 07:36 README.md
drwxrwxr-x 5 forge forge 4096 Feb 23 07:42 local
-rw-rw-r-- 1 forge forge 871 Feb 23 07:36 phpunit.xml
-rw-rw-r-- 1 forge forge 2034 Feb 23 07:36 please
drwxrwxr-x 3 forge forge 4096 Feb 23 08:51 public
drwxrwxr-x 11 forge forge 4096 Feb 23 07:36 site forge@somewebsite-online:~/somewebsite.online$ ls -al /home/forge/somewebsite.online/.git
total 1200
drwxrwxr-x 8 forge forge 4096 Feb 23 15:20 .
drwxrwxr-x 7 forge forge 4096 Feb 23 14:50 ..
-rw-rw-r-- 1 forge forge 22 Feb 23 15:19 COMMIT_EDITMSG
-rw-rw-r-- 1 forge forge 95 Feb 23 15:10 FETCH_HEAD
-rw-rw-r-- 1 forge forge 23 Feb 23 07:36 HEAD
-rw-rw-r-- 1 forge forge 41 Feb 23 15:10 ORIG_HEAD
drwxrwxr-x 2 forge forge 4096 Feb 23 07:36 branches
-rw-rw-r-- 1 forge forge 262 Feb 23 07:36 config
-rw-rw-r-- 1 forge forge 73 Feb 23 07:36 description
drwxrwxr-x 2 forge forge 4096 Feb 23 07:36 hooks
-rw-rw-r-- 1 forge forge 1166129 Feb 23 15:19 index
drwxrwxr-x 2 forge forge 4096 Feb 23 07:36 info
drwxrwxr-x 3 forge forge 4096 Feb 23 07:36 logs
drwxrwxr-x 88 forge forge 4096 Feb 23 15:05 objects
-rw-rw-r-- 1 forge forge 114 Feb 23 07:36 packed-refs
drwxrwxr-x 5 forge forge 4096 Feb 23 07:36 refs |
PS: The addon that creates the json files, also fires a data event, so it should theoretically be picked up by Spock? event(new FileUploaded('site/storage/addons/' . $this->getAddonClassName() . '/' . $androidBundleId . '.json')); |
Hey @madsem, sorry about the delay. Yes, the data event fired by your addon should theoretically picked up by Spock. This being back in February though, are you still having trouble with git pushing? |
@jesseleite I'm also seeing an issue with items being saved to Storage not getting staged. I'm using the BigKahuna addon, which uses Might be related: Eworm/big-kahuna#27 |
I'm trying to get Spock to work all day today, but no luck. It just doesn't really push most of the time and throws lots of errors in the log file.
Basically it doesn't even push new collection entries, it logs errors about index.lock files that it thinks exist, but that aren't there when I check the
/.git/
dir.I am ignoring Asset events, as all assets are on S3, and before Spock was also throwing errors about not finding the asset files, this is my
spock.yaml
:There were some successful pushes, but it's unreliable at best, for a while now I wasn't able to get it to push anything, always logs like the ones below.
These logs are from adding a single new entry:
Server: Ubuntu 18 / Nginx (Default Laravel Forge Setup)
Latest Statamic: 2.11.9
Spock 2.2.1
Repo Type: Private
The text was updated successfully, but these errors were encountered: