Rob
Can you show us your exact `satis.sjon` and the command you are running (even if it's a docker command or something)? Also > i've installed satis with composer, and therefore...
Yes, I think I was able to reproduce it. It has been a while though. I might have some time later today to look into it again.
Satis is not meant to be used as a mirroring tool for packagist.org, so we do not support this use-case.
1) No. 2) Satis always does a full scan. But it does use the composer cache for any source repositories that are of the vcs type. So it does not...
VCS should be "smarter". Normally you only use the more specific type if you want to provide custom options for said specific type of repository.
Not sure. Is the delay significant on every run? Or only the first run? (I.e. does caching help or not?) Would help if you could provide a verbose output log.
I think it is too much work to work around that requirement. So if it is a blocker for you, I recommend you stick to running an older version of...
Uhm.. not sure I follow. The problem is that some users have a `satis.json` that looks like this: ``` { "name": "my repository", ... } ``` This name is not...
Yeah, okay. I get it. But that seems like a lot of work for something that does not even directly address the original issue. The original issue is that the...
> I tried to verify that the satis package name is really used somewhere as an identifier inside the created repository metadata, but I had no luck finding it. Seems...