Explore >> Select a destination
|
You are here 
|
github.com | ||
| | | | |
nyveldt.com
|
|
| | | | | Adventures in code and other stories. | |
| | | | |
dbafromthecold.com
|
|
| | | | | In a previous post we went through how to use Docker Build Cloud to remotely build a Docker container image from a Github repository. In that example, we kicked off a build and pushed the image to a container registry using the syntax: - This all seems a bit manual, doesn't it? What if we... | |
| | | | |
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). | |
| | | | |
cfotech.com.au
|
|
| | | SAS experts predict mixed outcomes for the finance sector in 2024 due to the rise of generative AI and transformative tech. | ||
