Explore >> Select a destination
|
You are here 
|
erikbern.com | ||
| | | | |
ml-ops.org
|
|
| | | | | Machine Learning Operations | |
| | | | |
www.pulumi.com
|
|
| | | | | Learn platform engineering best practices in this 7-step guide, covering security, internal developer portals, self-service, and team-building for scalable success | |
| | | | |
www.harness.io
|
|
| | | | | [AI summary] This article discusses strategies for separating environment variables and infrastructure modules into distinct repositories to enhance security, scalability, and collaboration in DevOps practices. | |
| | | | |
tomasvotruba.com
|
|
| | | In a post from autumn, we looked at how to [develop packages in monorepo on PHP 8.1 and release a downgraded version on PHP 7.2](/blog/how-to-develop-sole-package-in-php81-and-downgrade-to-php72/). But having 2 repositories to work with still feels crappy. Which one should we use? Where do people contribute? Where do we report issues? Everyone needs clarification, and **time is wasted on explaining complexity**. I knew we could do better... we want **one repository**. Today I'll show you how to get there with 39 lines of GitHub Action workflow (including comments). | ||
