composer / satis

Simple static Composer repository generator - For a full private Composer repo use Private Packagist
MIT License
3.15k stars 519 forks source link

How Satis performs indexing #427

Open Icewild opened 7 years ago

Icewild commented 7 years ago

Hello there.

  1. Is there any possibility to configure Satis, so it will cache packages on demand, not all at once?
  2. How Satis do repeat scan? Download index and generating diff with local FS? Or Satis got any flags, so it won't need to do fullscan of working copy?
  3. If i have full mirror of packagist.org and i add new version of my private package directly to Satis, will i need to wait while Satis complete full rescan of my mirror to see a new version of my private package?
Icewild commented 7 years ago
  1. Is it normal that 8GB RAM is not enough to build index?
alcohol commented 7 years ago

Satis is not meant to be used as a mirroring tool for packagist.org, so we do not support this use-case.

Icewild commented 7 years ago

Ok, about third question i understand, but still, if it's not packagist.org? And could you please provide answers on other questions?

alcohol commented 7 years ago

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 always have to do a full git clone. But it will still scan all branches and tags.

staabm commented 6 years ago

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 always have to do a full git clone. But it will still scan all branches and tags.

Hmm we use repositories of type svn instead of vcs. Should we use vcs instead? Is there a difference whether we use vcs or one of the concrete versioning backends?

alcohol commented 6 years ago

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.