Skip to content
#

best-practices

Here are 918 public repositories matching this topic...

goldbergyoni
goldbergyoni commented Jan 26, 2020

Given the immense popularity of Docker and the need to harden it different per platform (see ideas below) - we'd like to start writing a Docker best practices section.

You're welcome to contribute ideas and write best practices - writing and brainstorming will people is an amazing way to deepen your Docker understanding.

At first, we want to collect ideas for best practices, solidify a list

brundozer
brundozer commented Jan 31, 2018

In 1.2, we can read the following:

You can use --autosquash to squash all your commits to a single commit. Nobody wants many commits for a single feature in develop branch. read more...

I think that asserting that nobody wants that is a fallacy. There are good reasons for which you would want to keep those commits separated even in develop branch:

  • know what the reason of a change wa
dipanjan77
dipanjan77 commented Aug 12, 2019

Description

Add a ReadMe file in the GitHub folder.
Explain usage of the Templates

Other Comments

Principles of NLP Documentation
Each landing page at the folder level should have a ReadMe which explains -
○ Summary of what this folder offers.
○ Why and how it benefits users
○ As applicable - Documentation of using it, brief description etc
Scenarios folder:

Improve this page

Add a description, image, and links to the best-practices topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the best-practices topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.