|
You are here |
forgejo.org | ||
| | | | |
jan.wildeboer.net
|
|
| | | | | As many of you know, I have moved almost all my repositories from Github to Codeberg a while ago. Now I want to take it to the next level: Build my own little CI/CD engine! | |
| | | | |
blog.michal.pawlik.dev
|
|
| | | | | In the previous post in the series I described the process of externalizing you HA (Home Assistant) using my custom addon. Make sure to check that out if you haven't already. This time I'll share the details of the add-on development process. First steps When building the add-on my first steps obviously went towards the existing online resources. The first thing I've found was the extensive tutorial on https://developers.home-assistant.io/docs/add-ons/tutorial, but there seems to be an easier hands-on approach. | |
| | | | |
www.shuttle.rs
|
|
| | | | | Implement Continuous Integration & Continuous Development effectively in your Rust project. | |
| | | | |
www.observeinc.com
|
|
| | | Model Context Protocol (MCP) servers are an emerging standard, and we're very excited to make the Observe MCP server available, so you can allow your agents to access your observability data. | ||