A debian repository server with support for signing packages, uploading to S3, and more
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.
 
 
Tyler 50f4709b4c Split out setupFilesystem to clean up the code 1 year ago
deb Fix tmpfs issues, add swapping of options, etc 1 year ago
packaging Fix build and packaging 1 year ago
samples Initial commit 4 years ago
.drone.yml Fix tmpfs issues, add swapping of options, etc 1 year ago
.gitignore Caching of packages, new config format 4 years ago
LICENSE.txt Initial commit 4 years ago
README.md Add b uild status, up version 1 year ago
apt.go Cleanup, fixes, cloud fs support 1 year ago
config.go Fix tmpfs issues, add swapping of options, etc 1 year ago
go.mod Fix tmpfs issues, add swapping of options, etc 1 year ago
go.sum Fix tmpfs issues, add swapping of options, etc 1 year ago
http.go Fix tmpfs issues, add swapping of options, etc 1 year ago
packages.go Fix tmpfs issues, add swapping of options, etc 1 year ago
sample_conf.ini Build proper packages 4 years ago
server.go Split out setupFilesystem to clean up the code 1 year ago

README.md

Build Status

deb-simple (get it? dead simple.. deb simple...)

A lightweight, bare-bones apt repository server.

Purpose

This project came from a need I had to be able to serve up already created deb packages without a lot of fuss. Most of the existing solutions I found were either geared at mirroring existing "official" repos or for providing your packages to the public. My need was just something that I could use internally to install already built deb packages via apt-get. I didn't care about change files, signed packages, etc. Since this was to be used in a CI pipeline it had to support remote uploads and be able to update the package list after each upload.

What it does:

  • Supports multiple versions of packages
  • Supports multi-arch repos (i386, amd64, custom, etc)
  • Supports uploading via HTTP/HTTPS POST requests
  • Supports removing packages via HTTP/HTTPS DELETE requests
  • Does NOT require a changes file
  • Supports uploads from various locations without corrupting the repo

What it doesn't do:

  • Create actual packages
  • Mirror existing repos

Usage:

Install using go get. Fill out the conf.json file with the values you want, it should be pretty self-explanatory, then fire it up!

Once it is running POST a file to the /upload endpoint:

curl -XPOST 'http://localhost:9090/upload?arch=amd64&distro=stable' -F "file=@myapp.deb"

Or delete an existing file:

curl -XDELETE 'http://localhost:9090/delete' -d '{"filename":"myapp.deb","distroName":"stable","arch":"amd64"}'

To use your new repo you will have to add a line like this to your sources.list file:

deb http://my-hostname:listenPort/ stable main

my-hostname should be the actual hostname/IP where you are running deb-simple and listenPort will be whatever you set in the config. By default deb-simple puts everything into the stable distro and main section. If you have enabled SSL you will want to swap http for https.

#License:

MIT so go crazy. Would appreciate PRs for anything cool you add though :)