--- title: "#configuration articles | Hashnode" description: "Explore 291 articles tagged #configuration on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/configuration" --- Tag # #configuration 291 posts · 5 followers [Powerduck](https://hashnode.com/@powerduck) · [Oct 28](https://hashnode.com/posts/agent-renamed-env-var-code-ci-kept-old-secret-name/6ae23e646ab42a8ef9cb3c9d) ### [The agent renamed the environment variable in code, but CI still held the old secret name](https://blogs.powerduck.com/agent-renamed-env-var-code-ci-kept-old-secret-name?utm_source=hashnode&utm_medium=feed) Renaming a token inside the repo does not rename the secret in CI. The agent updated every code reference, the local run passed, but the deployed read returned undefined under the old registered name. Local dotenv still carried the legacy alias, so nothing reproduced until after deploy. 3 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-renamed-env-var-code-ci-kept-old-secret-name?utm_source=hashnode&utm_medium=feed) [Powerduck](https://hashnode.com/@powerduck) · [Oct 28](https://hashnode.com/posts/agent-hardcoded-own-home-path-passed-locally/6ae222d23f1959c9b8800c54) ### [The agent hardcoded its own scratch path into the committed config and passed locally](https://blogs.powerduck.com/agent-hardcoded-own-home-path-passed-locally?utm_source=hashnode&utm_medium=feed) The agent moved a file-cache directory into config but wrote its own session scratch path as the default. It passed on the agent's own disk and failed on the next machine and in CI. Portable defaults resolve from the environment, never from the author's home. 2 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-hardcoded-own-home-path-passed-locally?utm_source=hashnode&utm_medium=feed) [Robin Sishodia](https://hashnode.com/@Sishodia) · [Oct 28](https://hashnode.com/posts/salesforce-custom-metadata-vs-custom-settings-cheat-sheet-deploy-hierarchy-and-admin-interview-q-a-day-22-30/6ae1fa6eabfb2f0925b16e0d) ### [Salesforce Custom Metadata vs Custom Settings Cheat Sheet: Deploy, Hierarchy and Admin Interview Q&A (Day 22/30)](https://sishodiarobin.hashnode.dev/salesforce-custom-metadata-vs-custom-settings-cheat-sheet-deploy-hierarchy-and-admin-interview-q-a-day-22-30?utm_source=hashnode&utm_medium=feed) Never hardcode a value. Pick the home that fits how it must travel. Custom metadata versus custom settings comes up in almost every admin interview. The 4 Building Blocks Block What it is Key poin 2 min read · [sishodiarobin.hashnode.dev](https://sishodiarobin.hashnode.dev/salesforce-custom-metadata-vs-custom-settings-cheat-sheet-deploy-hierarchy-and-admin-interview-q-a-day-22-30?utm_source=hashnode&utm_medium=feed) [Powerduck](https://hashnode.com/@powerduck) · [Oct 25](https://hashnode.com/posts/agent-fills-missing-config-with-silent-default/6add4cf5a114ff52457170b6) ### [The agent filled the missing config with a default and the misconfiguration went quiet](https://blogs.powerduck.com/agent-fills-missing-config-with-silent-default?utm_source=hashnode&utm_medium=feed) The required region setting was unset, so the agent added a hardcoded fallback instead of failing fast. The service booted cleanly and shipped against the wrong target; there was no error because the default made the missing input look optional. 4 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-fills-missing-config-with-silent-default?utm_source=hashnode&utm_medium=feed) [Kant Claude](https://hashnode.com/@kantclaude) · [Oct 16](https://hashnode.com/posts/make-your-config-fail-loudly-at-startup/6ad1b061911319bac5377a42) ### [Make Your Config Fail Loudly at Startup](https://kantclaude.hashnode.dev/make-your-config-fail-loudly-at-startup?utm_source=hashnode&utm_medium=feed) Few bugs are as annoying as the one that shows up three hours after a deploy, when the first request finally touches the code path that reads PAYMENT\_WEBHOOK\_SECRET, and it turns out nobody set it in 2 min read · [kantclaude.hashnode.dev](https://kantclaude.hashnode.dev/make-your-config-fail-loudly-at-startup?utm_source=hashnode&utm_medium=feed) [1](https://hashnode.com/posts/make-your-config-fail-loudly-at-startup/6ad1b061911319bac5377a42) [ara-ta3](https://hashnode.com/@ara-ta3) · [Oct 15](https://hashnode.com/posts/how-to-load-a-env-file-into-a-go-struct-with-viper/6ad07eaca7724e256eddf7cd) ### [How to Load a .env File into a Go Struct with Viper](https://ara-ta3.hashnode.dev/how-to-load-a-env-file-into-a-go-struct-with-viper?utm_source=hashnode&utm_medium=feed) Read a .env file in Go with Viper and decode its values into a struct using mapstructure tags. 3 min read · [ara-ta3.hashnode.dev](https://ara-ta3.hashnode.dev/how-to-load-a-env-file-into-a-go-struct-with-viper?utm_source=hashnode&utm_medium=feed) [江流石](https://hashnode.com/@jliushi) · [Oct 10](https://hashnode.com/posts/codex-cli-custom-relay-the-config-toml-you-actually-need/6aca23fc2b5f7893c13b47d4) ### [Codex CLI + Custom Relay: The config.toml You Actually Need](https://jliushi.hashnode.dev/codex-cli-custom-relay-the-config-toml-you-actually-need?utm_source=hashnode&utm_medium=feed) The minimum config to run Codex CLI through a third-party relay. Based on the AI Relay setup guide. Relays see your requests; pick one you trust. 1. Pick a relay that supports Codex Most relays on the 2 min read · [jliushi.hashnode.dev](https://jliushi.hashnode.dev/codex-cli-custom-relay-the-config-toml-you-actually-need?utm_source=hashnode&utm_medium=feed) [Jayesh Sojitra](https://hashnode.com/@jayeshsojitra) · [Aug 28](https://hashnode.com/posts/10-typescript-types-every-frontend-dev-should-know/6a91a613417a4f39bb5fa9f9) ### [10 TypeScript Types Every Frontend Dev Should Know](https://jayesh-sojitra.hashnode.dev/10-typescript-types-every-frontend-dev-should-know?utm_source=hashnode&utm_medium=feed) Most developers use TypeScript like it's JavaScript with extra colons. Here are 10 type features that actually change how safely you write code. 3 min read · [jayesh-sojitra.hashnode.dev](https://jayesh-sojitra.hashnode.dev/10-typescript-types-every-frontend-dev-should-know?utm_source=hashnode&utm_medium=feed) [1](https://hashnode.com/posts/10-typescript-types-every-frontend-dev-should-know/6a91a613417a4f39bb5fa9f9) [Mauricio Villegas](https://hashnode.com/@mauvilsa) · [Aug 10](https://hashnode.com/posts/a-cli-that-works-from-anywhere/6a79660c0760886d2da1ed57) ### [A CLI that works from anywhere](https://mauvilsa.hashnode.dev/a-cli-that-works-from-anywhere?utm_source=hashnode&utm_medium=feed) Turning a Python script into an installed command with pyproject.toml and an entry point, then giving it config files jsonargparse finds on its own. 8 min read · [mauvilsa.hashnode.dev](https://mauvilsa.hashnode.dev/a-cli-that-works-from-anywhere?utm_source=hashnode&utm_medium=feed) [Nicolas Fränkel](https://hashnode.com/@nfrankel) · [Jul 9](https://hashnode.com/posts/two-nasty-surprises-in-home-assistant-s-config/6a4fb8946cfccacfcdc2b52f) ### [Two nasty surprises in Home Assistant's config](https://frankel.hashnode.dev/two-nasty-surprises-in-home-assistant-s-config?utm_source=hashnode&utm_medium=feed) Last year, I motorized the rolling shutters on the southern façade of my apartment. My idea was to manage them via Home Assistant. I had a couple of automations in mind: In the evening, roll down the 4 min read · [frankel.hashnode.dev](https://frankel.hashnode.dev/two-nasty-surprises-in-home-assistant-s-config?utm_source=hashnode&utm_medium=feed)