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.
602 Commits
13 Branches
28 Tags
2.5 MiB
Branch: ng
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'ng'
${ noResults }
acmed/man/en/acmed.8

86 lines
1.9 KiB
Raw Permalink 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.24.0
1 month 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
​
​
​
​
​
​
Load the configuration
4 weeks 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
​
​
​
​
​
​
​
​
​
​
​
​
Load the configuration
4 weeks ago
Fix the "foregroung" typo I made the typo once and then copy/pasted it everywhere.
5 years ago
Load the configuration
4 weeks 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
Load the configuration
4 weeks ago
Add the `--no-pid-file` argument Fixes #60
3 years ago
Load the configuration
4 weeks 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
Load the configuration
4 weeks 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
​
​
Load the configuration
4 weeks 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
​
Load the configuration
4 weeks 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
​
Load the configuration
4 weeks 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 21, 2024
  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 DIR
  16. .Op Fl f|--foreground
  17. .Op Fl h|--help
  18. .Op Fl -no-pid-file
  19. .Op Fl -pid-file Ar FILE
  20. .Op Fl -root-cert Ar FILE
  21. .Op Fl V|--version
  22. .Sh DESCRIPTION
  23. .Nm
  24. is an Automatic Certificate Management Environment
  25. .Pq ACME
  26. client daemon which can automatically request and renew X.509 security certificates from various Certification Authorities
  27. .Pq CA .
  28. .Pp
  29. The options are as follows:
  30. .Bl -tag
  31. .It Fl c, -config Ar FILE
  32. Specify an alternative configuration directory.
  33. .It Fl f, -foreground
  34. Runs in the foreground.
  35. .It Fl h, -help
  36. Prints help information.
  37. .It Fl -no-pid-file
  38. Do not create any PID file.
  39. .It Fl -pid-file Ar FILE
  40. Specifies the location of the PID file.
  41. .It Fl -root-cert Ar FILE
  42. Add a root certificate to the trust store. This option can be used multiple times.
  43. .It Fl V, -version
  44. Prints version information.
  45. .El
  46. .Sh FILES
  47. .Bl -tag
  48. .It Pa /etc/acmed/conf-enabled
  49. Default
  50. .Nm
  51. configuration directory.
  52. .El
  53. .Sh SEE ALSO
  54. .Xr acmed.toml 5 ,
  55. .Xr tacd 8
  56. .Sh STANDARDS
  57. .Bl -hyphen
  58. .It
  59. .Rs
  60. .%A R. Barnes
  61. .%A J. Hoffman-Andrews
  62. .%A D. McCarney
  63. .%A J. Kasten
  64. .%D March 2019
  65. .%R RFC 8555
  66. .%T Automatic Certificate Management Environment (ACME)
  67. .Re
  68. .It
  69. .Rs
  70. .%A R.B. Shoemaker
  71. .%D February 2020
  72. .%R RFC 8737
  73. .%T Automated Certificate Management Environment (ACME) TLS Application-Layer Protocol Negotiation (ALPN) Challenge Extension
  74. .Re
  75. .It
  76. .Rs
  77. .Rs
  78. .%A R.B. Shoemaker
  79. .%D February 2020
  80. .%R RFC 8738
  81. .%T Automated Certificate Management Environment (ACME) IP Identifier Validation Extension
  82. .Re
  83. .El
  84. .Sh AUTHORS
  85. .An Rodolphe Bréard
  86. .Aq rodolphe@breard.tf