builds

Custom builds of assorted software. Some smaller projects live directly in this repo, but most have their own repos. It is a lot easier to work with CI systems that expect a 1:1 relationship between builds/projects and git repos.

projects

these builds are working (in use in the sudo.is infra) and can in theory be publicly used:

project	upstream	notes
airconnect	philippe44/AirConnect	docker only
blink1	todbot/blink1-tool	for the blink(1)
emacs	git.savannah.gnu.org/cgit/emacs.git	compiles emacs from source and publishes as .deb packages for ubuntu and debian (published on apt.sudo.is)
hass	home-assistant/core
hydrogen-web	vector-im/hydrogen-web	builds as static html/jss/css files, packaged as.deb. package (published on apt.sudo.is)
jellyfin-tizen	jellyfin/jellyfin-tizen
jenkins	jenkinsci/jenkins
owntone	owntone/owntone-server
playonlinux	PlayOnLinux
shairport	mikebrady/shairport-sync	docker only
socat-dns	N/A	using socat to forward the dns server for a bridged docker network
synapse-admin	Awesome-Technologies/synapse-admin

in progress / not ready

these builds are not ready yet, and are at various stages of 'in progress':

project	upstream	notes
calibre-web	janeczku/calibre-web
framework-ectool	DHowett/framework-ec
jellyfin-web	jellyfin/jellyfin-web
lldap	nitnelave/lldap
shields	badges/shields

Adding submodules

New submodule:

branch=main

# add submodule to track a branch
git submodule add -b $branch $url

# update submodule
git submodule update --remote

change existing submodule to track a branch

submodule=foo
branch=main

# change the submodule defintion in the parent repo
git config -f .gitmodules submodule.${submodule}.branch $branch

# and make sure the submodule itself is actually at that branch
cd $submodule
git checkout $branch
git branch -u origin/$branch $branch

repos

• git.sudo.is/ben/builds | upstream
• benediktkr/builds | mirror