vincent/aptly
1
0
Fork 0
mirror of https://github.com/aptly-dev/aptly.git synced 2026-06-04 05:10:40 +00:00
Code Issues Projects Releases Wiki Activity

update man page

Browse Source
This commit is contained in:
André Roth
2024-12-24 19:00:07 +01:00
parent 2c3a107e00
commit 65820cdf7a
2 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/aptly.1
+1 -1
View File
@@ -31,7 +31,7 @@ aptly looks for configuration file first in \fB~/\.aptly\.conf\fR then in \fB/us
With aptly version 1\.6\.0, yaml configuration with inline documentation is supported and recommended (see \fBdebian/aptly\.conf\fR)\.
.
.P
The legacy json configuration is still supported:
The legacy json configuration is still supported (and also supports comments):
.
.IP "" 4
.
man/aptly.1.ronn.tmpl
+3 -2
View File
@@ -21,9 +21,10 @@ aptly has integrated help that matches contents of this manual page, to get help
aptly looks for configuration file first in `~/.aptly.conf` then in `/usr/local/etc/aptly.conf` and `/etc/aptly.conf`. If no config file found (or they are not readable), a new one is created in the
home directory. If `-config=` flag is specified, aptly would use config file at specified location. Also aptly needs root directory for database, package and published repository storage. If not specified, directory defaults to `~/.aptly/`, it will be created if missing.
With aptly version 1.6.0, yaml configuration with inline documentation is supported and recommended (see `debian/aptly.conf`).
With aptly version 1.6.0, yaml configuration with inline documentation is
supported and recommended (see `debian/aptly.conf`).
The legacy json configuration is still supported:
The legacy json configuration is still supported (and also supports comments):
// vim: : filetype=json
// json configuration file with comments