Disclaimer

Technical content

An article reports either what we observed in the environment and versions it names, or what current primary sources said when we checked them. Both go stale: software changes underneath written instructions, and documentation is revised. A command that worked, or was documented, at the time of writing may behave differently on your machine, your runtime version or your provider.

Test anything you take from here in an environment you can safely break before you apply it to production. Commands that delete data, change infrastructure or rotate credentials deserve particular care.

AI assistance

We use AI assistance for parts of our work: drafting, translating between English and Korean, and scaffolding code. No article is published on the strength of a model's output alone. A person checks the claims, runs or reads the code, and confirms the sources before publication. Where an error survives that review, it is ours, and we will correct it.

No warranty and no professional advice

Content is provided without warranty of any kind, express or implied. It is not legal, financial, security or compliance advice, and it is not a guarantee that a described approach is appropriate for your systems, your data or your obligations. Decisions about your environment remain yours.

External links and third parties

An external link points at evidence — documentation, a repository, a changelog — and is not an endorsement. We do not control linked sites and are not responsible for their content or availability. Naming a product or a vendor implies no affiliation with, sponsorship by, or endorsement from that vendor.

This site carries no sponsored content and no paid links. No advertising is served on it at present.

Maintenance status

Each article shows whether it is maintained or kept as a historical record. A historical record is left online because it documents what was true at the time; it is not kept current. If something is out of date and matters to you, tell Restato Labs at [email protected] and see the editorial policy for how corrections are handled.