# configs Published articles for configs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Govern AI Behavior Like You Govern Releases DevFeed: [Govern AI Behavior Like You Govern Releases]() Original publisher: [Read original article]() Author: Nicole Morgan Published: 2026-09-17T14:41:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Artificial Intelligence](), [AI Agent](), [prompt](), [releases](), [Access Control](), [audit](), [jira]() Tags: [2026](), [access-control](), [agentic-ai](), [ai](), [audit](), [blog](), [configs](), [engineering](), [jira](), [prompt](), [releases]() ### AI overview The article argues that teams should manage prompts, models, and related settings as governed, testable AI Configs that can be changed at runtime without a redeploy. It describes progressive rollouts, experimentation, kill switches, policy checks, role-based access control, and audit logs as ways to govern AI behavior like software releases. ### Source excerpt Learn why leading engineering teams are managing prompts and models as AI Configs -- governed, testable, and changeable without a redeploy. | Blog ## This month in Mobian: May 2022 DevFeed: [This month in Mobian: May 2022]() Original publisher: [Read original article]() Author: Mobian team Published: 2022-05-31T23:59:59Z Content type: article Language: en Sources: [Mobian's Blog]() Topics: [Development](), [GitLab](), [ci](), [Debian](), [Kernel](), [systemd](), [Wiki]() Tags: [blog-posts](), [bugs](), [ci](), [configs](), [debian](), [gitlab](), [kernel](), [kernels](), [repositories](), [systemd](), [update](), [wiki]() ### AI overview A May 2022 Mobian development update covers monthly developer meetings, planned repository and developer-wiki moves toward Debian infrastructure, kernel and audio fixes, universal images for PinePhone devices, tow-boot limitations on PineTab, and a PinePhone Keyboard driver change. ### Source excerpt This is the first in a (hopefully) series of short blog posts summarizing what has happened in Mobianland. Given that Mobian integrates much of the ecosystem not developed by us, this report could reiterate many of the things being said somewhere else. Monthly dev meeting Despite being located all over the world (really!), we manage to meet in person once a month. Well, ok, "meet in person" means we conduct a jitsi video call. It is fun seeing all these sleepy faces where half of the people would like to go to bed already, while others wished they could have remained in bed longer. The TL;DR: we will attempt to move over more repositories from gitlab to salsa.debian.org (given gitlabs changes to the CI allowance we get, and in an attempt to align ourselves closer to Debian). In a similar move, the developer's wiki (NOT the user wiki) moves over to the Debian wiki. pondering if systemd-repart and systemd-growfs can maybe replace "growroot" We really should be opening a user-contrib section or something where contributed ports and kernels can live, e.g. for the Nexus 5. Planning stage. OnePlus 6 / Pocophone F1 Audio was broken due to a missing config option on 5.17 kernels, and was fixed by a subsequent update. Thanks to everyone who reported this issue and provided the information allowing us to fix it. Universal Images We have a universal mobian image that boots on the original Pinephone and the Pinephone Pro, however, there are still some bugs to iron out and kernel configs to be adapted. But overall, this looks promising. However, this will require some tool that can adapt configuration settings at runtime, based on the device it is currently running on. Tow-boot We were one of the earliest distributions to move over to tow-boot, and that worked out nearly well. However, there is a little catch: There is no tow-boot for the PineTab yet. So all images post-March 27, will not be able to install a U-boot if you have non installed yet. Help to port tow-boot to the Pin ## Flat Multi-Environment Config for Craft CMS 3 DevFeed: [Flat Multi-Environment Config for Craft CMS 3]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-02-29T15:29:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [.env](), [Environment Variables](), [configuration](), [Development]() Tags: [aliases](), [api-keys](), [approach](), [article](), [cms](), [config](), [configs](), [craft](), [database](), [docker](), [environment](), [environment-variables](), [file](), [files](), [flat](), [git](), [heroku](), [insights](), [multi-environment](), [need](), [presents](), [secrets](), [sorts](), [variables]() ### AI overview A tutorial on configuring Craft CMS 3 across development, staging, and production environments using aliases, environment variables, .env files, and configuration files. It presents a flat configuration approach and discusses keeping environment-specific credentials and secrets separate from source code and databases. ### Source excerpt Multi-environment configs for Craft CMS are a mix of aliases, environment variables, and config files. This article sorts it all out, and presents a flat config file approach ## Multi-Environment Config for Craft CMS DevFeed: [Multi-Environment Config for Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2016-12-02T20:32:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Development](), [Website]() Tags: [cms](), [configs](), [craft](), [effectively](), [efficacious](), [environment](), [environments](), [help](), [here-s](), [insights](), [multi-environment](), [production](), [project](), [settings](), [staging](), [strategy](), [work]() ### AI overview This tutorial explains how to configure a Craft CMS 2.5.x project for live, staging, and local environments. It covers environment-specific settings, including development mode, template caching, databases, passwords, file-system locations, and configuration overrides. ### Source excerpt Multi-environment configs help you work more effectively with Craft CMS. Here's an efficacious strategy