Explore >> Select a destination
|
You are here 
|
github.com | ||
| | | | |
dev.betterdoc.org
|
|
| | | | | At BetterDoc we're currently in the process of step by step replacing an old monolithic application with a microservice landscape. While adding services whe recognized that we needed to find a consistent pattern to naming these services to keep the "service zoo" organized. This post describes our overall scheme for naming our services. Note that since writing this blog post our idea of how a service should be named has changed and the following rules are no longer valid. Our most recent thoughts can be found here: (Naming things, part 3B). | |
| | | | |
ankane.org
|
|
| | | | | Git LFS allows you to version large files while storing them outside of your Git repository. Heroku doesn't have built-in support for it, so a few... | |
| | | | |
nyveldt.com
|
|
| | | | | Adventures in code and other stories. | |
| | | | |
benbrougher.tech
|
|
| | | How to use microk8s to create an ingress using MetalLB and the NGINX ingress controller | ||
