letsencrypt / letsencrypt/website
Other Client Options for bash should list acme.sh first
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 909
- Forks
- 591
- Avg merge
- 10h 40m
- Merged PRs (30d)
- 31
Description
When options are available, unless otherwise stated, users expect them to be listed in most-preferred (easiest-to-use, fastest, etc.) order.
On the Client Options page, the Bash list under Other Options mistakenly shows GetSSL first. GetSSL requires time-consuming editing of config files and has a dependency, cronie, that keeps it from running on (some or all) Debian-branch distros. (Even after building cronie from source.)
By contrast, acme.sh -- currently listed second -- is much quicker to deploy (following the simple guide) and is not distro-limited. It should therefore be listed first.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the Client Options page and inspect the Bash list under Other Options. Reorder the entries so acme.sh appears before GetSSL, then verify the rendered page and links show the requested order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100