Skip to content

Reusable code patterns which you can use as reference or copy to your project πŸ‘©β€πŸ’»πŸ‘¨β€πŸ³πŸ“–πŸ₯—

License

Notifications You must be signed in to change notification settings

MichaelCurrin/code-cookbook

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Code Cookbook πŸ‘©β€πŸ’»πŸ‘¨β€πŸ³πŸ“–πŸ₯—

Reusuable code patterns which you can use as reference or copy to your project

Cookbook overview

  • Recipe categories - start here browse topics and languages that interest you.
  • Make - Makefile samples
  • CI/CD
    • Many language-specific sample workflows for GH Actions to test and deploy your app
    • Plus some Netlify configs.
  • SEO
  • Shell - usage help and examples for commands and patterns to use one or more commands to solve a real problem. Such as how to do find and replace using find or sed or how to clean up your git repo.
  • Jekyll - code snippets and configs
  • Containers - commands and configs for using Docket and k8s.

Purpose

This is my collection of reusable code samples and instructions, arranged in a way like recipes so that you can use an entire file to solve a task and not just look for one line like in a cheatsheet guide.

Here you'll find code snippets in Jekyll, Bash, Python or JS. And some entire files you can copy in part or as a whole for your Makefile or deploy pipeline config.

Background

I have written and refined some of these recipes myself from my dev experience. Or I have copied from other sources like tutorials or other repos. I give credit as much as possible to the orginal source. Sometimes I don't even understand how a file works, but I know what it does and that it will be useful one day so I stash it as a reference in this centralized repo. This suits my learning style as I like to learn by example and real-world use, not just memorizing syntax and definitions.

This collection approach I use it also great because I can collect code by myself or others which solves similar problems or the same problem (e.g. deploy a site) and then I can compare the solutions. I can choose one that makes sense for my situation or I can take the best parts from each solution and make a new entry, which becomes my go-to solution for keeping my projects consistent.

Contributing

Contributions of new content or fixes are welcome. Please submit an issue or add a Pull Request from your forks's feature branch with a description of changes.

License

Released under MIT.