renken/shione
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
experimental debian packaging for shione.net
26 commits 2 branches 0 tags 234 KiB
Shell 100%
Find a file
Mohammed Amar-Bensaber 52ec354da9
ssh: limit overall login attempts and interactions 
Additionally also disable any unnecessary/unused features by default.
2024-10-08 22:49:47 +02:00
debian nginx: fix nginx default config path to be hidden 2024-10-08 22:49:01 +02:00
doc wireguard: document initial setup 2024-08-27 22:22:06 +02:00
files ssh: limit overall login attempts and interactions 2024-10-08 22:49:47 +02:00
.gitignore .gitignore: ignore misc artifacts and secret files 2024-08-27 22:22:05 +02:00
build.sh build: explicitly call gbp with --export-dir=WC 2024-08-27 22:40:56 +02:00
clean.sh clean: remove debhelper artifacts 2024-08-27 22:22:07 +02:00
LICENSE license: agplv3 2024-08-27 22:22:05 +02:00
README.md readme: init 2024-08-27 22:22:05 +02: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