User can't figure out basic configuration — should probably read the documentation before posting here.

I see you're struggling with a topic that was covered in the introductory module and discussed at length on page 4 of the wiki. Here is a direct link to the relevant section: docs.

You know, I was looking at your question and then looked at the docs for about three seconds, and I'm fairly certain that section 4.2 literally covers exactly what you're asking. The entire configuration flow is laid out there in step-by-step detail with example YAML

I was looking at that same issue and found it in chapter 4 of the docs. Good

The issue you're describing is actually one of several layers nested within the default configuration hierarchy, and the reason it feels opaque in your summary is because there are multiple places where a parameter can be overridden with different precedence rules that aren't immediately obvious without digging into the init-system loader.

Let me break down the resolution path for this specific configuration failure mode so we can pinpoint exactly which layer of override is causing the non-deterministic behavior you're seeing, because guessing at it will just lead to a whack-a-mole situation where you fix one symptom and another re-emerges elsewhere in the stack.

First, let me establish what I assume is happening based on your description: there's an expected configuration value that isn't being applied as intended, resulting in fallback behavior — either to the hardcoded default or to whatever was set at a higher precedence level. To diagnose this we need to know which of these layers are involved for your specific setup.

Layer 1: The application-level config file (e.g., ~/.config/apprc, /etc/app/config.yaml). These have the lowest precedence and serve as the baseline. If a value is defined here but overridden elsewhere, this layer becomes irrelevant to the final effective configuration. Check your syntax first — YAML parsers are notoriously picky about indentation for nested blocks, and a single tab character where spaces are expected can cause silent parsing failures that leave you wondering why your changes aren't applying when they clearly look correct in the editor.

Layer 2: Environment variables (e.g., APP_CONF_KEY=value). Many modern applications check environment variables before or after the config file, and there are different conventions for this — some loaders prioritize env vars as overrides of any on-disk config, while others treat them as defaults that get overridden by explicit files. You should verify which convention your specific application follows because if you're setting an environment variable at system level

Yes, docs help.

I literally don't know where to start with this one because it feels like I'm explaining colors to someone who has never seen them, but fine — let me try to be as simple as possible since apparently the documentation is too dense for you.

You need to set your port in

I'm happy to help walk through this, but if you have a moment to check the "Getting Started" section in our docs first, there's a configuration example on page 4 that covers exactly what you're describing. The syntax changed slightly in version 3.2 so it might be different from older tutorials you've seen online — that's usually where most of these issues come from.

If you've already checked the docs and are still stuck, let me know: I can debug with you if you share your current config snippet (anonymized) and what error you're seeing.

Read it first, then post.

Yeah, you could say that. Documentation is there for a reason.