Mirror
/
acmed
mirror of https://github.com/breard-r/acmed.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
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.
473 Commits
12 Branches
27 Tags
2.2 MiB
Tree: 9d43f72466
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9d43f72466'
${ noResults }
acmed/man/en/acmed.8

95 lines
2.2 KiB
Raw Normal View History

ACMEd v0.7.0
5 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
​
​
ACMEd v0.21.0
2 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
​
​
​
​
​
Fix the "foregroung" typo I made the typo once and then copy/pasted it everywhere.
5 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
​
Add the `--no-pid-file` argument Fixes #60
3 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
Fix the "foregroung" typo I made the typo once and then copy/pasted it everywhere.
5 years ago
​
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
​
​
​
​
​
Add the `--no-pid-file` argument Fixes #60
3 years ago
​
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
​
​
​
Fix the man pages syntax
4 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
​
​
​
Fix the man pages syntax
4 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
​
Fix the man pages syntax
4 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
​
​
​
​
​
​
​
​
​
RFC 8737 has been released
5 years ago
​
​
​
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
Implement IP identifiers RFC 8738: https://tools.ietf.org/html/rfc8738
4 years ago
​
​
​
​
​
​
​
Fix the man pages syntax
4 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
  1. .\" Copyright (c) 2019-2020 Rodolphe Bréard <rodolphe@breard.tf>
  2. .\"
  3. .\" Copying and distribution of this file, with or without modification,
  4. .\" are permitted in any medium without royalty provided the copyright
  5. .\" notice and this notice are preserved. This file is offered as-is,
  6. .\" without any warranty.
  7. .Dd Dec 19, 2022
  8. .Dt ACMED 8
  9. .Os
  10. .Sh NAME
  11. .Nm acmed
  12. .Nd ACME client daemon
  13. .Sh SYNOPSIS
  14. .Nm
  15. .Op Fl c|--config Ar FILE
  16. .Op Fl f|--foreground
  17. .Op Fl h|--help
  18. .Op Fl -log-stderr
  19. .Op Fl -log-syslog
  20. .Op Fl -log-level Ar LEVEL
  21. .Op Fl -no-pid-file
  22. .Op Fl -pid-file Ar FILE
  23. .Op Fl -root-cert Ar FILE
  24. .Op Fl V|--version
  25. .Sh DESCRIPTION
  26. .Nm
  27. is an Automatic Certificate Management Environment
  28. .Pq ACME
  29. client daemon which can automatically request and renew X.509 security certificates from various Certification Authorities
  30. .Pq CA .
  31. .Pp
  32. The options are as follows:
  33. .Bl -tag
  34. .It Fl c, -config Ar FILE
  35. Specify an alternative configuration file.
  36. .It Fl f, -foreground
  37. Runs in the foreground
  38. .It Fl h, -help
  39. Prints help information
  40. .It Fl -log-stderr
  41. Prints log messages to the standard error output
  42. .It Fl -log-syslog
  43. Sends log messages via syslog
  44. .It Fl -log-level Ar LEVEL
  45. Specify the log level. Possible values: error, warn, info, debug and trace.
  46. .It Fl -no-pid-file
  47. Do not create any PID file
  48. .It Fl -pid-file Ar FILE
  49. Specifies the location of the PID file
  50. .It Fl -root-cert Ar FILE
  51. Add a root certificate to the trust store. This option can be used multiple times.
  52. .It Fl V, -version
  53. Prints version information
  54. .El
  55. .Sh FILES
  56. .Bl -tag
  57. .It Pa /etc/acmed/acmed.toml
  58. Default
  59. .Nm
  60. configuration file.
  61. .El
  62. .Sh SEE ALSO
  63. .Xr acmed.toml 5 ,
  64. .Xr tacd 8
  65. .Sh STANDARDS
  66. .Bl -hyphen
  67. .It
  68. .Rs
  69. .%A R. Barnes
  70. .%A J. Hoffman-Andrews
  71. .%A D. McCarney
  72. .%A J. Kasten
  73. .%D March 2019
  74. .%R RFC 8555
  75. .%T Automatic Certificate Management Environment (ACME)
  76. .Re
  77. .It
  78. .Rs
  79. .%A R.B. Shoemaker
  80. .%D February 2020
  81. .%R RFC 8737
  82. .%T Automated Certificate Management Environment (ACME) TLS Application-Layer Protocol Negotiation (ALPN) Challenge Extension
  83. .Re
  84. .It
  85. .Rs
  86. .Rs
  87. .%A R.B. Shoemaker
  88. .%D February 2020
  89. .%R RFC 8738
  90. .%T Automated Certificate Management Environment (ACME) IP Identifier Validation Extension
  91. .Re
  92. .El
  93. .Sh AUTHORS
  94. .An Rodolphe Bréard
  95. .Aq rodolphe@breard.tf