The Freight configuration is a sourced shell script that defines a few important variables.
The Freight library directory. Typically /var/lib/freight.
The Freight cache directory. Typically /var/cache/freight. This should be the document root of the web server.
The architectures to support. Typically i386 amd64.
The Origin field in the Debian archive.
The Label field in the Debian archive.
The NotAutomatic field in the Debian archive.
The ButAutomaticUpgrades field in the Debian archive.
on to cache package control files or off to read them from the packages on each freight-cache(1) run.
The GPG key(s) to use. This value must be set either in a configuration file or by using the -g option to freight-cache(1). Multiple keys can be given to sign the repository with more signatures.
Pathname of a file containing the GPGP private key´s passphrase. This sets the --passphrase-fd and --passphrase-file options to gpg(1). The passphrase file can be set either in a configuration file or by using the -p option to freight-cache(1).
Message digest algorithm that GPG should use to sign the repository. Apt is phasing out SHA1 so it is recommended to use SHA512 for most use-cases. This sets the --personal-digest-preferences option to gpg(1). The digest algorithm can be set either in a configuration file or by using the -a option to freight-cache(1).
on to follow symbolic links in VARLIB to produce extra components in the cache directory or off to offer no special treatment.
The default configuration file.
User-specific configuration file.
- etc/freight.conf, .freight.conf
Directory-specific configuration files.
The pathname of an alternate configuration file.
The New Pornographers - "All the Old Showstoppers"
Richard Crowley email@example.com
freight-add(1) adds packages to the intermediate "Freight library" that is used by freight-cache(1) to build the actual repositories.
reprepro(1) manages Debian archives, too, if Freight isn´t your thing.
freight(1), freight-add(1), freight-cache(1), freight-clear-cache(1), freight-init(1).