updated readme file
parent
b26d0d8b71
commit
5b1126933e
33
README.md
33
README.md
|
@ -6,39 +6,20 @@ developer of the software I intend to run. Or if the recommended one is too
|
|||
complex for my specific use case. Or if I don't like it for whatever reason. Or
|
||||
if I just feel like making my own image.
|
||||
|
||||
Simply run `make $IMG_NAME` to build a specific image or run `make` to build them
|
||||
all.
|
||||
The created images are named as `rilla/$IMG_NAME`.
|
||||
|
||||
All images are made to suit my specific needs and taste, not to be generally
|
||||
useful.
|
||||
|
||||
I use simple Makefiles to build the images for the architectures I care about
|
||||
(linux/amd64 and linux/arm64) using `docker buildx` and push them to my private
|
||||
docker registry.
|
||||
|
||||
## Currently implemented images:
|
||||
|
||||
(many are self-explanatory)
|
||||
|
||||
* agate
|
||||
* archivebox
|
||||
* ansible
|
||||
* backup: simple image used in some of my backup daemons
|
||||
* buku: buku and bukuserver
|
||||
* ddclient
|
||||
* dendrite
|
||||
* filite
|
||||
* git-daemon: for git-daemon and git-http-backend
|
||||
* gitolite-pystagit: well, gitolite + pystagit
|
||||
* gitolite: gitolite + docker, so that I can mount the docker socket inside of
|
||||
it and have it do useful things through docker in response to triggers
|
||||
* monero
|
||||
* nfs-server
|
||||
* mpd
|
||||
* pleroma
|
||||
* rainloop
|
||||
* sassc
|
||||
* syncthing
|
||||
* tasks: intended to run a cron daemon to run arbitrary periodic tasks. I mount
|
||||
the docker socket inside of it to have it perform maintanance tasks outside
|
||||
of it's container.
|
||||
* tasks
|
||||
* tor
|
||||
* transmission
|
||||
* vdirsyncer
|
||||
* xandikos
|
||||
* webdav
|
||||
|
|
Loading…
Reference in New Issue