The code that drives my apt repository. https://apt.starbeamrainbowlabs.com
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

47 lines
2.7 KiB

  1. <!DOCTYPE html>
  2. <html>
  3. <head>
  4. <!--
  5. If you're reading this, then this is the header.html file used with Nginx's
  6. fancyindex thingy on apt.starbeamrainbowlabs.com. While you're welcome to
  7. use this file as a guide for your own apt repository, I suggest that you
  8. alter it to make it your own, as it contains a number specific references
  9. to my own personal apt repository.
  10. Note also that this file, once edited, must be symlinked into the repo
  11. directory (once it's created by aptosaurus.sh) manually - this isn't done
  12. automatically!
  13. -->
  14. <meta charset="utf-8" />
  15. <meta name="viewport" content="width=device-width" />
  16. <title>sbrl apt repository</title>
  17. <script>window.document.title = `${window.location.pathname} • sbrl apt repository`;</script>
  18. <link rel="stylesheet" href="/theme.css" />
  19. </head>
  20. <body>
  21. <p>This is the starbeamrainbowlabs.com apt repository.</p>
  22. <p>Add this repository to your debian-based system like this:</p>
  23. <pre><code># Add the repository
  24. echo "deb https://apt.starbeamrainbowlabs.com/ ./ # apt.starbeamrainbowlabs.com" | sudo tee /etc/apt/sources.list.d/sbrl.list
  25. # Import the signing key
  26. wget -q https://apt.starbeamrainbowlabs.com/aptosaurus.asc -O- | sudo apt-key add -
  27. # Alternatively, import the signing key from a keyserver:
  28. sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys D48D801C6A66A5D8
  29. # Update apt's cache
  30. sudo apt update</code></pre>
  31. <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>
  32. <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>
  33. <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>
  34. <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>
  35. <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>
  36. <h1>Index of