<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ops on Digital Archive Systems Tech Blog</title><link>https://tech.ldas.jp/en/tags/ops/</link><description>Recent content in Ops on Digital Archive Systems Tech Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 03 May 2026 18:00:00 +0900</lastBuildDate><atom:link href="https://tech.ldas.jp/en/tags/ops/index.xml" rel="self" type="application/rss+xml"/><item><title>A YAML-Driven Next.js Admin Console — Multiple Sites, Multiple Actions</title><link>https://tech.ldas.jp/en/posts/operator-console-yaml-driven-multi-action/</link><pubDate>Sun, 03 May 2026 18:00:00 +0900</pubDate><guid>https://tech.ldas.jp/en/posts/operator-console-yaml-driven-multi-action/</guid><description>&lt;blockquote>
&lt;p>This article is co-authored with a generative AI. Facts have been cross-checked against official documentation where possible, but errors may remain. Please verify against primary sources before making any important decisions.&lt;/p>&lt;/blockquote>
&lt;p>In an &lt;a href="https://tech.ldas.jp/en/posts/github-app-cloudflare-access-admin-console/">earlier post&lt;/a> I described an admin console for non-engineers, built on GitHub App + Cloudflare Access. This is a follow-up about making the console &lt;strong>add-a-site-without-touching-code&lt;/strong> ready, and about supporting &lt;strong>multiple actions per site&lt;/strong> (deploy, re-index, backup, …) cleanly.&lt;/p></description></item></channel></rss>