Unify HTTP requests and GRPC calls on a single domain for more flexible configuration: example with Woodpecker

Unify HTTP requests and GRPC calls on a single domain for more flexible configuration: example with Woodpecker
I installed the continuous integration service Woodpecker, to replace DroneCI, which the company that bought it decided to bury. As Woodpecker is a fork of the latest free version of Drone, its use is broadly similar. However, the teams have taken different directions on certain aspects, and communication with agents/runners, which used to be via websockets, is now carried out in Woodpecker using the GRPC protocol. The solution proposed by the Woodpecker documentation is to use 2 domains: one will be used for the web interface and the REST API, the second will be used for GRPC. [Read More]

Self-hosting: for a decentralized and responsible Internet

Self-hosting: for a decentralized and responsible Internet
In an idealized world, we would all be free to access any service, made available by a community motivated by the common good rather than by the penurious enrichment of a few. However, we don’t live in that world. Today, everything is monetized: the smallest product or service only exists if it brings in enough money, without regard for the common good. The apparent gratuity of digital services is often accompanied by a more discreet but lucrative counterpart: the exploitation of our personal data. [Read More]