lmdb: Update README
This commit is contained in:
parent
300f74fb10
commit
027358a340
|
@ -7,7 +7,7 @@ repositories. It is built on top of the official tools provided by the `pacman`
|
||||||
At this point the project is rather raw and there are many things left to implement and
|
At this point the project is rather raw and there are many things left to implement and
|
||||||
to improve (checkout the TODOs section below). Currently builds are exclusively triggered
|
to improve (checkout the TODOs section below). Currently builds are exclusively triggered
|
||||||
manually (although the API brings the possibility for automation), scalability is limited
|
manually (although the API brings the possibility for automation), scalability is limited
|
||||||
through the use of an in-memory database. Builds are only conducted on one host.
|
through the partial use of an in-memory database. Builds are only conducted on one host.
|
||||||
|
|
||||||
On the upside, this project can easily be used to together with other build scripts. It
|
On the upside, this project can easily be used to together with other build scripts. It
|
||||||
doesn't care if your repository's DB file is updated by another application; just be sure
|
doesn't care if your repository's DB file is updated by another application; just be sure
|
||||||
|
@ -334,6 +334,8 @@ editing the presets JSON file (e.g. `/etc/buildservice-git/presets.json` in the
|
||||||
|
|
||||||
## TODOs and further ideas for improvement
|
## TODOs and further ideas for improvement
|
||||||
* [ ] Use persistent, non-in-memory database (e.g. lmdb or leveldb) to improve scalability
|
* [ ] Use persistent, non-in-memory database (e.g. lmdb or leveldb) to improve scalability
|
||||||
|
* [x] Use db for packages
|
||||||
|
* [ ] Use db for build actions
|
||||||
* [ ] Allow triggering tasks automatically/periodically
|
* [ ] Allow triggering tasks automatically/periodically
|
||||||
* [ ] Allow to run `makechrootpkg` on a remote host (e.g. via SSH) to work can be spread across multiple hosts
|
* [ ] Allow to run `makechrootpkg` on a remote host (e.g. via SSH) to work can be spread across multiple hosts
|
||||||
* [ ] More advanced search options
|
* [ ] More advanced search options
|
||||||
|
|
Loading…
Reference in New Issue