OSTREE-ADMIN-SET-ORIGIN(1)
💖 NAME
ostree-admin-set-origin — change the "origin" (location for upgrades) 🛰️✨
okay so this is the ostree admin set-origin page — aka ostree-admin-set-origin — from the OSTREE ADMIN SET-OR(1) manual, and it’s all about changing where your upgrades are pointed. bestie, it’s giving “remote control for your deployment” energy 💅
🛰️ SYNOPSIS
ostree admin set-origin {REMOTENAME} {URL} [BRANCH]
🌸 DESCRIPTION
Okay so here’s the tea ☕: this command adds a new remote named REMOTENAME (if it does not already exist). Then it changes the origin file for the current deployment. That origin is the ref that will be "tracked" and upgraded with ostree admin upgrade 🔥👑
✨ OPTIONS ✨
--set=KEY=VALUE— set an option for the remote 🎀--index=INDEX— change the origin of the deployment numberedINDEX(starting from0) 🦋
🎀 EXAMPLE
Here’s the example, copied exactly with zero edits, because we do not mess with commands 💖:
$ ostree admin set-origin exampleos http://os.example.com/repo
exampleos/10.0/main/router
💖 cute sign-off: source/version is OSTree, the manual footer label is OSTREE ADMIN SET-OR(1), and the date isn’t printed in the footer — so no date to report, bestie 🎀✨
📦 where this page comes from
- arch rolling: ostree 2026.6-1 · LGPL-2.0-or-later
- 💖 girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms