You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To simplify the installation of cheat & cheatsheets, I created docker-cheat which packages both projects in a single 9 MB docker image. As it may be useful to others as well, I went ahead and linked the project here - specifically from the 'Related Projects' and 'Installing' wiki pages.
However, I noticed neither page is linked by the README. Is that intentional? For example, I was quite surprised when I read on 'Installing' that there are 'cheat' OS packages, a fact that the README fails to mention.
The text was updated successfully, but these errors were encountered:
Regarding the README situation - yeah, I'm aware that it doesn't link to the wiki currently, and I agree that's not ideal. I've omitted the link because the wiki is a bit of a mess currently. I don't really know what's in there anymore, and there isn't much structure to the content.
I'm going to make a pass through it in the near-term to tidy things up a bit (and add some more information), and I'll create a README link when I'm happy with it.
I'll leave this ticket open until then as a reminder to do so.
Thanks @bannmann!! Adding alias cheat='docker run --rm bannmann/docker-cheat' worked great for me as it was batteries included (no config file not found errors, no downloading external cheatsheets, etc.).
To simplify the installation of cheat & cheatsheets, I created docker-cheat which packages both projects in a single 9 MB docker image. As it may be useful to others as well, I went ahead and linked the project here - specifically from the 'Related Projects' and 'Installing' wiki pages.
However, I noticed neither page is linked by the README. Is that intentional? For example, I was quite surprised when I read on 'Installing' that there are 'cheat' OS packages, a fact that the README fails to mention.
The text was updated successfully, but these errors were encountered: