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.
307 Commits
12 Branches
27 Tags
2.2 MiB
Tree: b75b8ba9f7
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'b75b8ba9f7'
${ noResults }
acmed/man/en/acmed.8

92 lines
2.1 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.12.0
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 "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
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
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
​
​
​
​
​
​
​
​
​
​
​
​
​
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 September 26, 2020
  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 -pid-file Ar FILE
  22. .Op Fl -root-cert Ar FILE
  23. .Op Fl V|--version
  24. .Sh DESCRIPTION
  25. .Nm
  26. is an Automatic Certificate Management Environment
  27. .Pq ACME
  28. client daemon which can automatically request and renew X.509 security certificates from various Certification Authorities
  29. .Pq CA .
  30. .Pp
  31. The options are as follows:
  32. .Bl -tag
  33. .It Fl c, -config Ar FILE
  34. Specify an alternative configuration file.
  35. .It Fl f, -foreground
  36. Runs in the foreground
  37. .It Fl h, -help
  38. Prints help information
  39. .It Fl -log-stderr
  40. Prints log messages to the standard error output
  41. .It Fl -log-syslog
  42. Sends log messages via syslog
  43. .It Fl -log-level Ar LEVEL
  44. Specify the log level. Possible values: error, warn, info, debug and trace.
  45. .It Fl -pid-file Ar FILE
  46. Specifies the location of the PID file
  47. .It Fl -root-cert Ar FILE
  48. Add a root certificate to the trust store. This option can be used multiple times.
  49. .It Fl V, -version
  50. Prints version information
  51. .El
  52. .Sh FILES
  53. .Bl -tag
  54. .It Pa /etc/acmed/acmed.toml
  55. Default
  56. .Nm
  57. configuration file.
  58. .El
  59. .Sh SEE ALSO
  60. .Xr acmed.toml 5 ,
  61. .Xr tacd 8
  62. .Sh STANDARDS
  63. .Bl -hyphen
  64. .It
  65. .Rs
  66. .%A R. Barnes
  67. .%A J. Hoffman-Andrews
  68. .%A D. McCarney
  69. .%A J. Kasten
  70. .%D March 2019
  71. .%R RFC 8555
  72. .%T Automatic Certificate Management Environment (ACME)
  73. .Re
  74. .It
  75. .Rs
  76. .%A R.B. Shoemaker
  77. .%D February 2020
  78. .%R RFC 8737
  79. .%T Automated Certificate Management Environment (ACME) TLS Application-Layer Protocol Negotiation (ALPN) Challenge Extension
  80. .Re
  81. .It
  82. .Rs
  83. .Rs
  84. .%A R.B. Shoemaker
  85. .%D February 2020
  86. .%R RFC 8738
  87. .%T Automated Certificate Management Environment (ACME) IP Identifier Validation Extension
  88. .Re
  89. .El
  90. .Sh AUTHORS
  91. .An Rodolphe Bréard
  92. .Aq rodolphe@breard.tf