From fd4c7d2dd302cd64cec57c74536d4dbcada2941d Mon Sep 17 00:00:00 2001
From: Harald Pfeiffer <coding@lirion.de>
Date: Sun, 23 Mar 2025 07:41:16 +0100
Subject: Rename repo to packages.lirion.de, move aptly stuff to aptly
 subfolder

---
 aptly/etc/aptly-lirionde.conf | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 aptly/etc/aptly-lirionde.conf

(limited to 'aptly/etc/aptly-lirionde.conf')

diff --git a/aptly/etc/aptly-lirionde.conf b/aptly/etc/aptly-lirionde.conf
new file mode 100644
index 0000000..34f8ac3
--- /dev/null
+++ b/aptly/etc/aptly-lirionde.conf
@@ -0,0 +1,18 @@
+# vim:syntax=sh
+# Repos that should be snapshotted and added to the publication:
+MYREPS=(
+	"repo1"
+	"repo2"
+)
+# The GPG key with which we will sign the repositories.
+GPGKEY='1A7EDEADBEEFBADC0FFEE0123456789ABCDEF012'
+# A test public key to which we will encrypt a temporary string to check
+# whether GPG works at all:
+GPGTESTKEY='1A7EDEADBEEFBADC0FFEE0123456789ABCDEF012'
+# Packages base folder. Structure is:
+# BASEFOLDER/reponame/package.deb
+PBASE="/tmp/aptly"
+# Base folder where packages are being published. Assumption is that
+# aptly is configured to use $TBASE for all operations except for the
+# resulting repo which will be managed and live in $TBASE/public.
+TBASE="/var/cache/repos/aptly"
-- 
cgit v1.2.3