aptosaurus/header.html

49 righe
3.0 KiB
HTML

<!DOCTYPE html>
<html>
<head>
<!--
If you're reading this, then this is the header.html file used with Nginx's
fancyindex thingy on apt.starbeamrainbowlabs.com. While you're welcome to
use this file as a guide for your own apt repository, I suggest that you
alter it to make it your own, as it contains a number specific references
to my own personal apt repository.
Note also that this file, once edited, must be symlinked into the repo
directory (once it's created by aptosaurus.sh) manually - this isn't done
automatically!
-->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width" />
<title>sbrl apt repository</title>
<script>window.document.title = `${window.location.pathname} • sbrl apt repository`;</script>
<link rel="stylesheet" href="/theme.css" />
</head>
<body>
<p>This is the starbeamrainbowlabs.com apt repository.</p>
<p><strong>PSA:</strong> Nomad, Consul, and Vault will no longer be updated in this repository in protest of the BSL licence change.<br />If anyone knows of a good alternative that isn't Kubernetes (or if it is Kubernetes, you better have a very good guide on integrating it into an *existing* network with an *existing* DNS and DHCP server setup), please get in touch.</p>
<p>Add this repository to your debian-based system like this:</p>
<pre><code># Add the repository
echo "deb https://apt.starbeamrainbowlabs.com/ ./ # apt.starbeamrainbowlabs.com" | sudo tee /etc/apt/sources.list.d/sbrl.list
# Import the signing key
wget -q https://apt.starbeamrainbowlabs.com/aptosaurus.asc -O- | sudo apt-key add -
# Alternatively, import the signing key from a keyserver:
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys D48D801C6A66A5D8
# Update apt's cache
sudo apt update</code></pre>
<p>Packages in this repository are automatically signed by aptosaurus, my apt repository bot. While every caution has been taken to avoid signing things we shouldn't, you should still exercise caution.</p>
<p>While packages in this repository primarily come from continuous integration / deployment, package updates are normally stashed and released every day at 2am, to ease updates for clients.</p>
<p>A human-readable summary of the packages available in this repository can be found in <a href="/SUMMARY.txt"><code>SUMMARY.txt</code></a>, which is automatically generated from the source packages in the repo.</p>
<p>Note that while older versions of packages <em>do</em> exist in this repository, packages more than 3 versions out of date are now automatically deleted to save on disk space. If you need really old versions, download them and keep them as backups ☺</p>
<p>Finally, as many CPU architectures will be attempted to be supported here as possible. If binary packages are being released by a project, they are probably packaged here. The exception to this is the 32-bit x86 architecture. This is deprecated by many Linux distributions - so effort is not made to package it here (though if you've got a valid use-case get in touch and I'll see if I can help).</p>
<h1>Index of