Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

On success, print a message that contains the absolute path of the .lego directory. #2236

Open
1 task done
offby1 opened this issue Jul 25, 2024 · 0 comments
Open
1 task done

Comments

@offby1
Copy link

offby1 commented Jul 25, 2024

Welcome

  • Yes, I've searched similar issues on GitHub and didn't find any.

How do you use lego?

Binary

Detailed Description

I spent a while yesterday running lego run, which appeared to succeed (i.e., it emitted messages that suggested it had generated certificates), and yet when I then examined the current directory (which had normal permissions -- 0775 iirc), there was no .lego directory in it.

After much head-scratching, I figured out what happened:

  • I'd installed lego via "snap" as opposed to, say "apt" or manually
  • snaps are weird :-).
  • The lego program ran inside a container, with a not-obvious-to-me working directory (namely /var/snap/lego/common/); all my certificates and keys &c were there.

So: if lego had, as its final act, printed a message like Saved certifcates and keys to /var/snap/lego/common/.lego, that'd have saved me a bunch of time.

# for free to join this conversation on GitHub. Already have an account? # to comment
Development

No branches or pull requests

2 participants