mlops
Ctrlk
  • MLops
  • MLops
    • Chap 0. Before everything
    • Chap 1. Tools for developers
    • Chap 2. Hardware
    • Chap 3. Infrastructure/platform design
    • Chap 4. Toolkit/codebase
      • 4.3 Packaging
      • 4.0 good to have
        • package your commonly used funcs using conda
        • publish commonly used base image to docker hub
        • set up jenkins and customized config
        • a template for PR in the .github/
        • pylint: code style
        • docstring
        • Have a folder for dev, and test other formal code
        • unit test
        • logging
        • how to report bugs effectively
        • type checking
        • Keep a good Changelog
      • 4.1 toolkits template
      • 4.2 DL-specific
    • Chap 5. Paper reproduction
    • Chap 6. Prototype development
    • Chap 7. Deployment and model serving
    • Chap 8. Productionization/Maintenance/Adoption
    • Chap 9. PR/keep stoa
    • Acknowledge
  • DataOps
    • Chap 0. Preface
    • Chap 1. Data engineering
    • Chap 2. Data integration
    • Chap 3. Data security/privacy
    • Chap 4. Data quality
  • MODELOPS
    • Chap 0. Intro
    • Chap 1. Model registery
  • Fun Facts about Image
    • Chap 0. Preface
    • Chap 1. Process
    • Chap 2. Metrics
    • Chap 3. Case Study
  • Softskills
    • Chap 1. Mindsets
    • Chap 2. Soft skills in getting things done
    • Chap 3. Portfolio and side projects
    • Chap 4. Mentorship
Powered by GitBook
On this page

Was this helpful?

  1. MLops
  2. Chap 4. Toolkit/codebase

4.0 good to have

package your commonly used funcs using condapublish commonly used base image to docker hubset up jenkins and customized configa template for PR in the .github/pylint: code styledocstringHave a folder for dev, and test other formal codeunit testlogginghow to report bugs effectivelytype checkingKeep a good Changelog
Previous4.3 PackagingNextpackage your commonly used funcs using conda

Last updated 4 years ago

Was this helpful?