starred/certbot-certbot-1
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-08-02 03:22:14 +02:00
Code Issues Packages Projects Releases Wiki Activity

There's no need to use certbot-auto here. (#6970)

Browse Source 
I came across this when looking through our docs for other references to certbot-auto.

For the README changes, I deleted a bunch of duplicated and outdated instructions in favor of pointing people to https://certbot.eff.org.
This commit is contained in:
Brad Warren
2019-04-22 09:14:20 -07:00
committed by GitHub
parent a58ad22002
commit a817e4f0ec
2 changed files with 6 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.rst
+5 -33
View File
@@ -30,43 +30,15 @@ If you'd like to contribute to this project please read `Developer Guide
.. _installation: .. _installation:
Installation
------------
The easiest way to install Certbot is by visiting `certbot.eff.org`_, where you can
find the correct installation instructions for many web server and OS combinations.
For more information, see `Get Certbot <https://certbot.eff.org/docs/install.html>`_.
.. _certbot.eff.org: https://certbot.eff.org/
How to run the client How to run the client
--------------------- ---------------------
In many cases, you can just run ``certbot-auto`` or ``certbot``, and the The easiest way to install and run Certbot is by visiting `certbot.eff.org`_,
client will guide you through the process of obtaining and installing certs where you can find the correct instructions for many web server and OS
interactively. combinations. For more information, see `Get Certbot
<https://certbot.eff.org/docs/install.html>`_.
For full command line help, you can type::
./certbot-auto --help all
You can also tell it exactly what you want it to do from the command line.
For instance, if you want to obtain a cert for ``example.com``,
``www.example.com``, and ``other.example.net``, using the Apache plugin to both
obtain and install the certs, you could do this::
./certbot-auto --apache -d example.com -d www.example.com -d other.example.net
(The first time you run the command, it will make an account, and ask for an
email and agreement to the Let's Encrypt Subscriber Agreement; you can
automate those with ``--email`` and ``--agree-tos``)
If you want to use a webserver that doesn't have full plugin support yet, you
can still use "standalone" or "webroot" plugins to obtain a certificate::
./certbot-auto certonly --standalone --email admin@example.com -d example.com -d www.example.com -d other.example.net
.. _certbot.eff.org: https://certbot.eff.org/
Understanding the client in more depth Understanding the client in more depth
-------------------------------------- --------------------------------------
docs/using.rst
+1 -1
View File
@@ -923,7 +923,7 @@ files that can be found in ``/etc/letsencrypt/renewal``.
By default no cli.ini file is created, after creating one By default no cli.ini file is created, after creating one
it is possible to specify the location of this configuration file with it is possible to specify the location of this configuration file with
``certbot-auto --config cli.ini`` (or shorter ``-c cli.ini``). An ``certbot --config cli.ini`` (or shorter ``-c cli.ini``). An
example configuration file is shown below: example configuration file is shown below:
.. include:: ../examples/cli.ini .. include:: ../examples/cli.ini