lmiklosko/apt-repository repository overview

Trusted APT repository based on ubuntu and apt-ftparchive.

Getting started

• First you need to prepare the directory which will be used as a source for the deb packages. It has to follow the standardized structure as demonstrated below: /srv/www/deb
  ├── dists
     └── stable
     ├── devel
     │   ├── binary-amd64
     │   ├── binary-armhf
     │   └── binary-i386
     ├── main
        ├── binary-amd64
        ├── binary-armhf
        └── binary-i386
  Please note that Package files are generated for each architecture separately, so you'll have a package file in each binary-* directory. Furthermore the Release files are generated on distribution basis, so in the above example you'd have only one Release file.

• To use the container, you need to mount the volume with your deb files as /data. (-v /path/to/your/deb/files:/data) and forward the port 80. The image automatically monitors changes to this mount and regenerates Package and Release files if necessary. In order to trigger manual generation, execute apt-regenerate script in the docker container by using: docker exec <container_id> /usr/local/bin/apt-regenerate

From now on, you can enjoy your fully automated APT repository without worrying about Package files regeneration :)

Signing the release files
For advanced uses, the image allows to generate Release.gpg and InRelease files alongside Release file. For this you have to import your private key into container's gpg by using docker exec command. Next, you need to update the passphrase in /usr/local/bin/apt-regenerate on lines 34 and 36. Once done, script will automatically generates signed release files for you.