# Self-hosted Self-hosting is the practice of running software on infrastructure controlled by its operator instead of a third-party provider. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How libreboot.org is hosted DevFeed: [How libreboot.org is hosted]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: article Language: en Sources: [News about Libreboot releases and development]() Topics: [Self-hosted](), [hosting](), [Internet](), [static-site-generator](), [Git](), [forgejo]() Tags: [article](), [bios](), [canoeboot](), [coreboot](), [free-software](), [github](), [hosting](), [internet](), [libre](), [libreboot](), [opensource](), [self-hosted](), [static-site-generator](), [uefi]() ### AI overview The article introduces the Federation of Freedom, or Fedfree, a website launched in December 2022 to teach people how to self-host internet servers using libre software. It documents the hosting setup used by libreboot.org and plans to add guides for mail, rsync, cgit, and Forgejo. The project aims to help people avoid defaulting to proprietary hosting services. ### Source excerpt Article: How libreboot.org is hosted Web link: https://libreboot.org/news/fedfree.html ## Nextcloud Hub 26 Summer Released, Euro-Office Desktop App Coming Soon DevFeed: [Nextcloud Hub 26 Summer Released, Euro-Office Desktop App Coming Soon]() Original publisher: [Read original article]() Author: Christian Rakoot Published: 2026-09-16T18:32:34Z Content type: release Language: en Sources: [Self Host Lab]() Topics: [Nextcloud](), [Open Source](), [Self-hosted](), [microsoft 365]() Tags: [collaboration](), [desktop](), [feature](), [microsoft-365](), [news](), [office](), [open-source](), [release](), [self-hosted]() ### AI overview Nextcloud Hub 26 Summer is live, with the Euro-Office desktop app announced for release in the coming weeks. The update also includes faster browser-based Office features and partner-contributed tools for teams, calendar resource booking, and Tables. ### Source excerpt Nextcloud's Hub 26 Summer is live today, headlined by a new Euro-Office desktop app arriving in the coming weeks, plus features co-built with partners including IONOS, SURF, and the German state of Schleswig-Holstein. ## n8n Patches 16 Security Vulnerabilities, 12 Rated High Severity DevFeed: [n8n Patches 16 Security Vulnerabilities, 12 Rated High Severity]() Original publisher: [Read original article]() Author: Christian Rakoot Published: 2026-09-16T18:31:20Z Content type: news Language: en Sources: [Self Host Lab]() Topics: [n8n](), [Vulnerabilities](), [patches](), [Security](), [Self-hosted]() Tags: [automation](), [n8n](), [news](), [patches](), [security](), [security-vulnerabilities](), [self-hosted](), [update](), [vulnerabilities]() ### AI overview n8n published a bi-weekly security update disclosing 16 fixed advisories: 12 rated High severity and 4 rated Medium. The article highlights an unauthenticated NoSQL injection in the MongoDB Chat Memory node that can disclose chat history across sessions, along with five High-severity credential-handling advisories. ### Source excerpt n8n, the self-hosted workflow automation platform covered regularly on this site, published its bi-weekly security update on September 16, 2026. The bulletin, posted on the official n8n Community forum by a member of the n8n security team, discloses 16 advisories fixed since the previous update on September 2: 12 rated High severity and 4 rated [...] ## Running a Self-Hosted Tailscale Control Server Behind a Reverse Proxy DevFeed: [Running a Self-Hosted Tailscale Control Server Behind a Reverse Proxy]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-15T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [tailscale](), [proxy](), [traefik](), [TLS (Transport Layer Security)](), [TLS handshake](), [Self-hosted](), [Homelab]() Tags: [dns](), [docker](), [h2](), [homelab](), [networking](), [proxy](), [reverse-proxy](), [security](), [self-hosted](), [tailscale](), [tls](), [tls-handshake](), [traefik]() ### AI overview This tutorial explains how to run a self-hosted Tailscale control server, Headscale, behind Traefik. It finds that the reverse proxy must use TLS with HTTP/1.1 only because Tailscale's noise handshake expects a full-duplex byte stream and can fail when ALPN negotiates HTTP/2. ### Source excerpt Headscale behind Traefik: tls.options=no-h2@file with alpnProtocols http/1.1, because the Tailscale noise handshake breaks when ALPN negotiates h2. ## Seven Reliability Tests for Home Lab Services DevFeed: [Seven Reliability Tests for Home Lab Services]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-13T12:34:15Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Self-hosted](), [Containers](), [Network](), [Proxmox]() Tags: [home-lab](), [home-server](), [network](), [proxmox](), [self-hosted](), [server]() ### AI overview The article presents seven reliability tests for home lab services, including disconnecting Internet access and stopping one container in a redundant setup. It explains how these tests can reveal dependencies on external resources and weaknesses in DNS and service design. ### Source excerpt When it comes to putting a new service into the home lab that is something I will feel like I can rely on and trust, it has to be able... The post I Don't Trust a Home Lab Service Until It Passes These 7 Tests appeared first on Virtualization Howto. ## IBM Research and Red Hat benchmark llm-d serving GLM-5.2 on H100 GPUs DevFeed: [IBM Research and Red Hat benchmark llm-d serving GLM-5.2 on H100 GPUs]() Original publisher: [Read original article]() Author: Peter Hess Published: 2026-09-08T12:00:00Z Content type: article Language: en Sources: [IBM Research]() Topics: [Inference](), [GPU](), [Self-hosted](), [Large Language Model](), [ibm]() Tags: [ai](), [ai-for-code](), [generative-ai](), [gpu](), [hybrid-cloud](), [hybrid-cloud-platform](), [ibm](), [inference](), [llm](), [news](), [open-source](), [scaling-ai](), [self-hosted]() ### AI overview IBM Research, Red Hat, and collaborators report a benchmark deployment of the llm-d open-source inference framework serving the open-weight GLM-5.2 model on 544 NVIDIA H100 GPUs. The reported workload reached more than 6.6 million output tokens per minute and up to 3,000 concurrent coding agents without preemptions. ### Source excerpt IBM Research and Red Hat deployed a 753B open model on H100 GPUs, serving thousands of concurrent coding agents at 5-10x lower cost than commercial APIs. ## Introducing worker topologies for self-hosted Appwrite DevFeed: [Introducing worker topologies for self-hosted Appwrite]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-07T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Self-hosted](), [Containers](), [Coroutines](), [Docker Compose]() Tags: [announcements](), [compose](), [container](), [containers](), [coroutines](), [self-hosted]() ### AI overview Appwrite introduces two worker topologies for self-hosted instances. The combined topology is now the default and runs background work in two containers, while the separate topology preserves one container per queue and scheduler for installations needing independent scaling or resource controls. ### Source excerpt Self-hosted Appwrite now runs all background workers in a single container by default. Learn how the combined topology works and when to scale out with separate workers. ## Appwrite 2.0 is now available for self-hosting DevFeed: [Appwrite 2.0 is now available for self-hosting]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-07T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Self-hosted](), [PostgreSQL](), [Containers]() Tags: [containers](), [postgresql](), [products](), [self-hosting](), [upgrade]() ### AI overview Appwrite 2.0 is available for self-hosting. It introduces a rebuilt Console, PostgreSQL as the default database for new installations, a coroutine-based server engine, and a combined worker topology that reduces the default instance from 33 to 16 containers. Existing installations retain their current database when upgraded. ### Source excerpt Appwrite 2.0 brings a rebuilt Console, PostgreSQL as the default database, and a combined worker topology that runs your instance on 16 containers instead of 33. ## Introducing Postgres to self-hosted Appwrite DevFeed: [Introducing Postgres to self-hosted Appwrite]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-07T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Self-hosted](), [Databases](), [Docker]() Tags: [database](), [docker](), [install](), [mongodb](), [postgres](), [products](), [self-hosted]() ### AI overview Appwrite 2.0 makes Postgres the default database for new self-hosted installations. The setup wizard also lets users choose MariaDB or MongoDB. Existing installations keep their current database, and migration to another database is not supported. ### Source excerpt Appwrite 2.0 runs new self-hosted instances on Postgres by default. Choose Postgres, MariaDB, or MongoDB in the setup wizard when you install. ## Self-Hosted Platform Build Order: Dependencies from Bare Metal to Model Serving DevFeed: [Self-Hosted Platform Build Order: Dependencies from Bare Metal to Model Serving]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-04T07:00:00Z Content type: article Language: en Sources: [Philipp Lehmann]() Topics: [Self-hosted](), [Ansible](), [Kubernetes](), [ceph](), [observability](), [model-serving](), [Compose]() Tags: [ansible](), [architecture](), [article](), [ceph](), [compose](), [infrastructure-as-code](), [kubernetes](), [model-serving](), [observability](), [self-hosted]() ### AI overview This article explains the dependency order for building a self-hosted platform. It covers consistent bare-metal inventory, Ansible configuration convergence, networking, Kubernetes, Ceph storage, identity, observability, and model serving. ### Source excerpt Self-hosted platform build order: why mesh, cluster, Ceph storage, identity and observability must precede model serving, shown with Compose depends_on. ## UniFi ENAS vs 45Drives X15: Comparing Two Rackmount NAS Systems DevFeed: [UniFi ENAS vs 45Drives X15: Comparing Two Rackmount NAS Systems]() Original publisher: [Read original article]() Author: Rob Andrews Published: 2026-08-31T16:00:55Z Content type: comparison Language: en Sources: [NAS Compares]() Topics: [Enterprise NAS](), [Hardware](), [Self-hosted](), [Ubiquiti](), [Server](), [Containers](), [virtual machines]() Tags: [45-drives](), [45-drives-2026](), [45-drives-2027](), [45-drives-nas](), [45drives](), [45drives-2026](), [45drives-2027](), [45drives-nas](), [45drives-review](), [45drives-system](), [45drives-unraid](), [45drives-vs-cloud](), [45drives-vs-netapp](), [45drives-vs-qnap](), [45drives-vs-synology](), [45drives-vs-unifi](), [45drives-x15](), [45drives-x15-vs-unifi-enas](), [comparison](), [containers](), [enterprise-nas](), [hardware](), [nas](), [network-attached-storage-nas](), [self-hosting](), [ubiquiti](), [uncategorised](), [unifi](), [unifi-2026](), [unifi-2027](), [unifi-enas](), [unifi-enas-review](), [unifi-nas](), [unifi-nas-comparison](), [unifi-nas-review](), [unifi-review](), [unifi-unas](), [virtual-machines]() ### AI overview This comparison examines the UniFi ENAS and 45HomeLab X15 rackmount NAS systems, covering their hardware, storage architectures, connectivity, operating-system services, management models, and upgrade paths. It presents the ENAS as a centrally managed UniFi Drive and ZFS appliance, while the X15 combines a 45Drives chassis with an x86 workstation platform and a lifetime Unraid licence for broader self-hosting and homelab use. ### Source excerpt UniFi vs 45Drives NAS Servers for Business.- Which Should You Buy? The UniFi ENAS and 45HomeLab X15 sit in a relatively narrow part of the storage market, positioned above conventional desktop NAS systems but below many fully configured enterprise storage platforms. Both are sold without storage media, use rackmount steel enclosures, provide at least 15 [...] ## Security Caveat: Locked out of my server while traveling DevFeed: [Security Caveat: Locked out of my server while traveling]() Original publisher: [Read original article]() Author: Josh Sherman Published: 2026-08-30T00:00:00Z Content type: opinion Language: en Sources: [Josh Sherman]() Topics: [Self-hosted](), [Security](), [Linode](), [Firewall](), [hosting](), [DDoS]() Tags: [command](), [ddos](), [firewall](), [hosting](), [linode](), [security](), [self-hosting]() ### AI overview A personal account of being unable to access a self-hosted server while traveling because firewall rules restricted services and ports to specific IP addresses. The author describes using Linode's web-hosted shell to add a temporary nomadic IP address to the allow list, then plans to remove it afterward. ### Source excerpt I'm still on my self-hosting kick as of late, while also questioning my life choices around hosting my own git forge. The last week or so has included what appears to be a DDoS attack rather than some coordinated scraping effort by a sketchy LLM company. Open source will prevail, even if I'm being stubborn about giving in and setting up Anubis. WordPress has been its own other adventure, but this isn't meant to be a post about those security caveats. I'll save those for another week. The current dilemma is that I'm far from home, ~30 hours away up in Rhode Island. I'm sitting at Audrey's Coffee House & Lounge, where it was a bit too early to order a BLT. As I sat down to knock out a quick blog post, I realized very quickly that I didn't think things through as well as I had thought. I keep my servers pretty well hardened, including but not limited to limiting access to certain services / ports to specific IP addresses. This tends to not be much of a problem. I do a lot of work from the house, which in itself is a problem I want to remedy in the near future. I also boss agents around remotely, but they are all homebodies as well. Since I like to stay as close to the server as possible, I try to not introduce managed services except where I feel it's absolutely necessary. In this scenario, I use iptables via the ufw command. I don't run a large enough fleet that I'd feel like leveraging Linode's firewall would be beneficial. Path of least resistance today would be to simply compose a blog post and get it live when I'm back home. Could probably just ask one of my friendly robots to take the markdown file and get it out there for me too. But alas, I would prefer to figure out how to pull this off, then blog about it. All while thinking through alternatives so future Josh can look back at this post and ask, "so why didn't you actually do anything you talked about in this post?" This dance probably looks about the same with most modern VPS hosting providers, but my story ## Preloading Knowledge Into a Model Instead of Retrieving It DevFeed: [Preloading Knowledge Into a Model Instead of Retrieving It]() Original publisher: [Read original article]() Author: Avi Chawla Published: 2026-08-24T17:13:39Z Content type: tutorial Language: en Sources: [Daily Dose of Data Science]() Topics: [Retrieval Augmented Generation (RAG)](), [Caching](), [long-context](), [Inference](), [Self-hosted](), [model-deployment](), [GPU]() Tags: [caching](), [compute](), [context-window](), [deployment](), [inference](), [rag](), [retrieval](), [self-hosted](), [storage]() ### AI overview This article introduces a three-part RAG Systems course about preloading a knowledge corpus into a model's stored KV cache so subsequent queries can skip retrieval, chunking, and embedding. It covers naive, compressed, modular, and trained preloading, along with context limits, provider and self-hosted economics, cache compression constraints, and production deployment. ### Source excerpt How to process your corpus once, skip retrieval entirely, and serve every query from a stored cache. Three parts covering the full spectrum. ## How Razorpay Cut Its Metrics Bill by 62% Without Losing a Dashboard DevFeed: [How Razorpay Cut Its Metrics Bill by 62% Without Losing a Dashboard]() Original publisher: [Read original article]() Author: Dhairya Mehta Published: 2026-08-24T10:25:21Z Content type: article Language: en Sources: [Razorpay Engineering - Medium]() Topics: [Monitoring](), [migration](), [incident](), [Self-hosted](), [telemetry]() Tags: [cost](), [high-availability](), [incident](), [metrics](), [migration](), [monitoring](), [self-hosted]() ### AI overview Razorpay reduced daily metrics ingestion from about 450 billion to about 170 billion samples, cutting its metrics bill by 62% without deleting useful dashboards or breaking alerts. The article describes an audit conducted during a planned migration from a self-hosted VictoriaMetrics cluster to a managed monitoring platform, covering scrape intervals, duplicate high-availability scrapes, and high-cardinality metrics. ### Source excerpt Contributor: Saijal Shrivastava We cut our metrics ingestion by 62% without deleting a single useful dashboard or breaking an alert. Daily ingestion dropped from about 450 billion samples to about 170 billion. The surprising part was not one large optimization. It was three simple discoveries hiding in plain sight: Scrape intervals can multiply ingestion. High-availability scraping can silently send duplicate metrics when deduplication happens only at the storage layer. High-cardinality metrics are easy to create, expensive to keep, and hard to remove without ownership. We found these while preparing to move from a self-hosted VictoriaMetrics cluster to a managed monitoring platform. The migration started as a reliability project. The audit turned it into a cost and signal-quality project. We were not just moving monitoring data. We were moving years of accumulated assumptions about what was worth scraping. The Incident that Forced the Audit Our self-hosted VictoriaMetrics cluster had served us well for years. Then one storage node hit EBS volume throttling. Traffic shifted to the remaining storage nodes, the extra load pushed another node past its limits, and the storage layer collapsed. We saw the same pattern whenever a storage node became unavailable: traffic redistributed, the remaining nodes overloaded, and the cluster moved back toward failure. The collection, ingestion, and query components were still running, so the system looked alive from the outside. But the storage layer was down. Metrics stopped being persisted. Dashboards went blank. Alerts stopped evaluating. Recovery took hours. Teams fell back to logs and manual checks to understand production health. Figure 1: Cascading failure in the pipeline That made the reliability problem obvious. We needed a more stable monitoring architecture. We evaluated several options: self-hosted designs with disaster recovery built in, and fully managed alternatives. But when we priced the managed options, one number ## Using a Local Proxy to Centralize AI Tool Routing, Logging, and Policy DevFeed: [Using a Local Proxy to Centralize AI Tool Routing, Logging, and Policy]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-18T07:00:00Z Content type: article Language: en Sources: [Philipp Lehmann]() Topics: [proxy](), [API](), [audit](), [configuration](), [Self-hosted]() Tags: [api](), [audit](), [configuration](), [llm](), [proxy](), [python](), [security](), [self-hosted]() ### AI overview The article proposes routing every model-using tool on a developer machine through one local proxy. This centralizes endpoint selection, request logging, auditing, and enforcement of policies such as keeping sensitive project code on a self-hosted model. It notes that tools with hardcoded or otherwise unsupported upstream configuration can bypass the proxy. ### Source excerpt OPENAI_BASE_URL=http://localhost:8080/v1 for every AI tool: one local FastAPI proxy that logs each request and refuses internal-only projects. ## Where Apollo MCP Server Stands on the OWASP MCP Top 10 DevFeed: [Where Apollo MCP Server Stands on the OWASP MCP Top 10]() Original publisher: [Read original article]() Author: Camille Lawrence Published: 2026-08-14T17:11:10Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [Model Context Protocol](), [MCP Server](), [audit](), [Shared Responsibility Model](), [configuration](), [GraphQL](), [Rust](), [Self-hosted]() Tags: [announcement](), [apollo](), [apollo-mcp-server](), [audit](), [configuration](), [graphql](), [hardening](), [mcp](), [mcp-server](), [rust](), [self-hosted](), [shared-responsibility]() ### AI overview This article evaluates Apollo MCP Server against all ten risks in the latest reviewed OWASP MCP Top 10 revision. It finds that the server's architecture directly closes one risk because typed GraphQL operations are parsed and type-checked without shell execution. The remaining risks require configuration, monitoring, and team-owned security decisions. ### Source excerpt Architecture alone closes 1 of the ten risks in OWASP's MCP Top 10. See how Apollo MCP Server scores on the rest, and which configuration choices remain yours. ## August 2026 product update: hosted MCP and more DevFeed: [August 2026 product update: hosted MCP and more]() Original publisher: [Read original article]() Author: Joshua Wood Published: 2026-08-12T07:00:00Z Content type: release Language: en Sources: [Honeybadger]() Topics: [Model Context Protocol](), [MCP Server](), [OAuth](), [Self-hosted](), [AI Agent]() Tags: [2026](), [agent](), [company-updates](), [developer-tools](), [hosted-mcp-server](), [mcp](), [oauth](), [product](), [python](), [search](), [self-hosting](), [update]() ### AI overview Honeybadger's August 2026 product update introduces OAuth for its hosted MCP server, adds EU support for self-hosting, and announces natural-language error search, anomaly alerts, and Oban-py support. ### Source excerpt This cycle: OAuth on the hosted MCP server, EU support for self-hosting it, natural-language error search, anomaly alerts, and Oban-py support. ## SecretSpec 0.19: Moving and importing secrets between providers DevFeed: [SecretSpec 0.19: Moving and importing secrets between providers]() Original publisher: [Read original article]() Author: domenkozar Published: 2026-08-11T23:15:09Z Content type: release Language: en Sources: [Announcements - NixOS Discourse]() Topics: [configuration](), [Self-hosted](), [servers]() Tags: [announcements](), [config](), [generate](), [json](), [moving](), [providers](), [release](), [secrets](), [self-hosted](), [servers](), [verify]() ### AI overview SecretSpec 0.19 introduces provider-specific secret storage layouts, safer imports with verification before deletion, value transformations, configuration stored alongside secrets, ephemeral values and runtime prompts, Passbolt support, and faster remote-provider operations. ### Source excerpt Hey all, secretspec 0.19 is out with highlights: Provider-specific storage layouts: map one application variable to each provider's native item, field, vault, or path. Safer imports: preflight every source and destination, verify copied values, and only then delete the source. Value transforms: decode Base64 or hexadecimal values and extract fields from JSON documents. Config in secrets: resolve committed, profile-specific configuration alongside provider-backed secrets. Ephemeral values and runtime prompts: generate or securely request values that should exist for only one invocation. Passbolt support: read and write secrets in self-hosted Passbolt servers. Faster remote providers: attach local caches directly to authoritative providers and batch 1Password field reads. Read the full release post: SecretSpec 0.19: Moving and importing secrets between providers | SecretSpec Disclaimer: LLMs have been used 1 post - 1 participant Read full topic ## Self-Hosted LLM Inference: Serving, Benchmarking and Agent Guardrails DevFeed: [Self-Hosted LLM Inference: Serving, Benchmarking and Agent Guardrails]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-07T07:00:00Z Content type: article Language: en Sources: [Philipp Lehmann]() Topics: [Self-hosted](), [Large Language Model](), [Inference](), [model-serving](), [benchmarking](), [LLM evaluation / benchmarking](), [API]() Tags: [agents](), [api](), [benchmarking](), [guardrails](), [inference](), [llm](), [ollama](), [security](), [self-hosted](), [testing]() ### AI overview This article examines self-hosted LLM inference for infrastructure work, focusing on data locality, local-versus-hosted model tradeoffs, repeatable benchmarking on personal tasks, model serving, and guardrails for agents that can propose or apply changes. ### Source excerpt Ollama OpenAI-compatible /v1/chat/completions: a repeatable benchmark on your own tasks and a dry-run plus --approve guardrail for infrastructure agents. ## July product update: Remote MCP server, Projects API and more DevFeed: [July product update: Remote MCP server, Projects API and more]() Original publisher: [Read original article]() Author: Aishwari Pahwa Published: 2026-08-05T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [MCP Server](), [Model Context Protocol](), [releases](), [OAuth](), [Authorization](), [API](), [SDKs](), [Command-line interface](), [Self-hosted]() Tags: [ai](), [api](), [authorization](), [claude-code](), [cli](), [mcp](), [mcp-server](), [oauth](), [product](), [products](), [python](), [releases](), [remote-mcp-server](), [sdk](), [self-hosted](), [update]() ### AI overview Appwrite's July 2026 product update introduces a hosted remote MCP server with OAuth, a Projects API, OAuth Device Authorization for the CLI, and Appwrite 1.9.6 for self-hosted deployments. ### Source excerpt See what's new in Appwrite with the hosted remote MCP server Projects API OAuth Device Authorization and Appwrite 1.9.6. ## A Polyline Is Not a Route DevFeed: [A Polyline Is Not a Route]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-03T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [API](), [Routing (disambiguation)](), [Open Source](), [Self-hosted](), [Server]() Tags: [api](), [backend](), [code](), [implementation](), [open-source](), [route](), [routing](), [self-hosted](), [server]() ### AI overview This article explains a Codename One maps routing API that converts coordinates into road-following routes and provides geometry, distance, duration, alternatives, legs, and step instructions. It describes the callback behavior, encoded geometry support, and use of OSRM as the default service, while noting that the public demonstration server is unsuitable for production and that applications can use a self-hosted or other provider. ### Source excerpt The new Codename One maps routing API turns coordinates into road-following geometry, distance, duration, legs, and steps through OSRM or an application-defined service. ## How Yandex Cloud built and open-sourced Farm for preview environments DevFeed: [How Yandex Cloud built and open-sourced Farm for preview environments]() Original publisher: [Read original article]() Author: DakEnviy0 (Яндекс, Yandex Cloud & Yandex Infrastructure) Published: 2026-07-30T07:29:36Z Content type: article Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [Docker](), [Kubernetes](), [Self-hosted](), [Development](), [Node.js]() Tags: [dev](), [docker](), [farm](), [frontend](), [js](), [kubernetes](), [node](), [node-js](), [preview](), [preview-87a227230297](), [self-hosted](), [tag-4004cf5948d3](), [tag-92292b2c626f](), [tag-e6d9cc1f0757]() ### AI overview The article describes how Yandex Cloud developed Farm, a service that creates preview environments for pull requests. It traces the system's evolution from a self-hosted script on one virtual machine to an orchestrator using Docker and Kubernetes, and explains the motivation for open-sourcing it. ### Source excerpt Каждый пул-реквест хочется не просто проверить тестами, а показать вживую -- дизайнеру, менеджеру, соседней команде, чтобы все они смогли потыкаться в UI -- порадоваться, понаходить баги -- порасстраиваться. Казалось бы, что сложного: поднял окружение и дал ссылку. Но когда пул-реквесты сыпятся десятками в день, а команд целое множество, "просто поднять окружение" превращается в отдельный инфраструктурный проект. Привет, Хабр! Меня зовут Михаил Гольбах, я ведущий разработчик интерфейсов Yandex Cloud. Уже несколько лет мы с командой развиваем Ферму -- сервис, который поднимает preview-окружение под каждый пулл-реквест. В этой статье расскажу, как Ферма выросла из простого self-hosted-скрипта на одной виртуальной машине в оркестратор на Docker и Kubernetes и почему в итоге мы открыли её код. Читать далее ## Best Bitbucket Alternatives in 2026 DevFeed: [Best Bitbucket Alternatives in 2026]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-07-29T11:54:28Z Content type: comparison Language: en Sources: [Semaphore Engineering]() Topics: [bitbucket](), [CI/CD](), [GitHub Actions](), [GitLab](), [Self-hosted](), [Cloud](), [Deployment](), [DevSecOps]() Tags: [2026](), [alternatives](), [bitbucket](), [ci-cd](), [circleci](), [cloud](), [compare](), [github](), [github-actions](), [gitlab](), [gitlab-ci](), [linux](), [macos](), [pipelines](), [self-hosted]() ### AI overview This comparison guide examines Bitbucket Pipelines and four alternatives--Semaphore, GitHub Actions, GitLab CI/CD, and CircleCI--to help teams choose a CI/CD platform based on source-control ecosystem, visibility, deployment control, hosting model, and operational requirements. ### Source excerpt Bitbucket Pipelines is a logical starting point for teams already using Bitbucket Cloud. It is built into the source-control experience, configured in a bitbucket-pipelines.yml file, and offers both Atlassian-hosted execution and self-hosted runners. But convenience at the repository level is not always the same thing as the best long-term CI/CD operating model. Teams evaluating Bitbucket [...] The post Best Bitbucket Alternatives in 2026 appeared first on Semaphore. ## Connect OpenSearch to private ML endpoints DevFeed: [Connect OpenSearch to private ML endpoints]() Original publisher: [Read original article]() Author: Nathalie Jonathan Published: 2026-07-28T15:00:41Z Content type: tutorial Language: en Sources: [OpenSearch]() Topics: [Amazon OpenSearch Service](), [network security](), [VPC](), [inference-endpoints](), [Security](), [AWS IAM](), [Latency](), [Self-hosted](), [Amazon Web Services]() Tags: [aws](), [aws-identity-and-access-management-iam](), [blog](), [firewalls](), [inference](), [infrastructure](), [opensearch](), [production](), [self-hosted](), [vpc]() ### AI overview This guide explains how to connect OpenSearch and Amazon OpenSearch Service to machine learning models hosted on private infrastructure. It covers VPC-hosted endpoints, private SageMaker endpoints, internal API gateways, and self-hosted inference servers, with configuration steps for connectors, model registration, deployment, testing, and VPC egress. ### Source excerpt Connect OpenSearch to ML models hosted on private infrastructure. Configure ML Commons connectors for VPC-hosted endpoints, private SageMaker models, and internal inference servers without exposing services to the public internet The post Connect OpenSearch to private ML endpoints appeared first on OpenSearch. [Next page]()