Morning Dose of Git

Some fool has checked .settings, .project, and myCrazyProductionDB.properties files into your git repo. You can add them to .gitignore, but they’ll still show up as modified because they are already being tracked. If you really can’t delete them, you can at least stop tracking them with:

$ git update-index --assume-unchanged <file>

A Simple Example

$ git update-index --assume-unchanged .classpath

If Git needs to modify the file, it will fail gracefully. To merge changes, you’ll have to un-mark it as assume-unchanged.

To see which files you’ve marked:

$ git ls-files -v | grep "^[[:lower:]]"
h .classpath

This works because ls-files -v prints the marked file in lower-case.

Re-mark the file with:

$ git update-index --no-assume-unchanged .classpath
share this:Email this to someoneTweet about this on TwitterShare on LinkedInShare on Facebook

linkedOut – Microservices

WTF is a microservice? Martin Folwer’s Microservices a definition of this new architectural term.

Richard Clayton exposes some potential pitfalls in Failing at Microservices. Please avoid our mistakes.

Reduce the risk of failing at a new technology by hacking your organization to better manage ‘skill debt’. Oren Ellenbogen responds to the painful example of failure with some excellent suggestions in, Who should own your engineering team’s skill debt?.

What makes a good microservice? Behold, the 12 factors.

Matt Stine’s book can help you migrate to a cloud native architecture.

share this:Email this to someoneTweet about this on TwitterShare on LinkedInShare on Facebook