renken/shione
1
0
Fork 0
Code Issues 11 Pull requests Projects Releases Packages Activity Actions
experimental debian packaging for shione.net
41 commits 2 branches 0 tags 290 KiB
Shell 100%
Find a file
Mohammed Amar-Bensaber 188153fb34
build: init qemu-based staging setup 
I emphasize that it's a quote-on-quote staging setup, not really a
proper one yet but hopefully it'll be.

TODO: Maybe look into AWS MicroVM as an alternative to QEMU?
2025-03-20 21:39:45 +01:00
debian nginx: ensure package builds and installs properly 2025-03-16 23:33:37 +01:00
doc wireguard: document initial setup 2024-08-27 22:22:06 +02:00
files nginx: ensure package builds and installs properly 2025-03-16 23:33:37 +01:00
.gitignore fixup! forgejo 2025-03-19 21:17:23 +01:00
build.sh build: cache forgejo binary instead of always re-downloading 2025-03-16 23:33:55 +01:00
clean.sh clean: remove debhelper artifacts 2024-08-27 22:22:07 +02:00
init.sh init: apt update and install apt-utils only once 2025-03-16 23:33:55 +01:00
LICENSE license: agplv3 2024-08-27 22:22:05 +02:00
qemu.sh build: init qemu-based staging setup 2025-03-20 21:39:45 +01:00
README.md readme: init 2024-08-27 22:22:05 +02:00
setup_qemu.sh build: init qemu-based staging setup 2025-03-20 21:39:45 +01:00
TODO.md todo: integrate deb-systemd-invoke 2024-08-27 22:22:07 +02:00

README.md

Shione.net

Experimental Debian packaging and configuration. This project is mainly for educational purposes. However, the aim is to package shione-specific configuration in a way that would allow deployment to be reproducible.

Package-specific configuration

Because shione runs GNU/Linux Debian, I wish to transform per-package config into .deb packages themselves. This project is basically an application of config-package-dev. This will allow me to integrate the modifications I introduce to the said packages within the Debian packaging system which comes with many benefits.

  1. Quickly rebuild a host machine from scratch if needed.
  2. Know the configuration state of each machine using the package manager.
  3. Automatically update configuration by updating the system itself.
  4. Integrate complex post-installation configuration, possibly such as introducing cron jobs (is it possible?) as part of the configuration package.

Project hierarchy

It is not yet clear to me how I'll do this. I'm thinking perhaps about having a single source package that produces multiple "binary" packages. Each one would be a package-specific configuration. Standalone packages not specific to shione will probably reside in their own git repository under the Debian section.

References