README: remove "Keeping git repository disk usage under control" section
New script utils/index does an automatic call to `git gc --auto` and if it detects a gc.log file, it runs `git gc --aggressive`. There shouldn't be any reason for people to have to think about that aspect. Remove that info from the README and make it lighter weight. Signed-off-by: Théo Lebrun <theo.lebrun@bootlin.com>
This commit is contained in:
parent
f17c56dc09
commit
0e9954b702
1 changed files with 0 additions and 23 deletions
23
README.adoc
23
README.adoc
|
|
@ -261,29 +261,6 @@ through a daily cron job.
|
|||
You can set `$ELIXIR_THREADS` if you want to change the number of threads used by
|
||||
update.py for indexing (by default the number of CPUs on your system).
|
||||
|
||||
== Keeping git repository disk usage under control
|
||||
|
||||
As you keep updating your git repositories, you may notice that some can become
|
||||
considerably bigger than they originally were. This seems to happen when a `gc.log`
|
||||
file appears in a big repository, apparently causing git's garbage collector (`git gc`)
|
||||
to fail, and therefore causing the repository to consume disk space at a fast
|
||||
pace every time new objects are fetched.
|
||||
|
||||
When this happens, you can save disk space by packing git directories as follows:
|
||||
|
||||
----
|
||||
cd <bare-repo>
|
||||
git prune
|
||||
rm gc.log
|
||||
git gc --aggressive
|
||||
----
|
||||
|
||||
Actually, a second pass with the above commands will save even more space.
|
||||
|
||||
To process multiple git repositories in a loop, you may use the
|
||||
`utils/pack-repositories` that we are providing, run from the directory
|
||||
where all repositories are found.
|
||||
|
||||
= Building Docker images
|
||||
|
||||
Dockerfiles are provided in the `docker/` directory.
|
||||
|
|
|
|||
Loading…
Reference in a new issue