<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>flove making-of — Gitea questions</title>
    <link>https://flove.org/making-of.html</link>
    <description>New Gitea design questions from flove interviews.</description>
    <language>en</language>
    <item>
      <title>Public host for provenance / commit links (GIT_BASE public)?</title>
      <link>https://flove.org/making-of.html#talk2web-refine_q1</link>
      <guid isPermaLink="false">talk2web-refine_q1</guid>
      <category>Gitea</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Public Gitea at git.flove.org — Stand up a public Gitea; commit + wiki links resolve for everyone. Most self-hosted-aligned.
• Mirror to GitHub (floveorg) — Push a mirror; link to GitHub commits. Easy reach, less FOSS-pure.
• Keep localhost only — Links work only on your machine; public visitors get no provenance.

★ decided: Public Gitea at git.flove.org · ◇ recommended: Public Gitea at git.flove.org</description>
    </item>
    <item>
      <title>Commit + push making-of on every recording?</title>
      <link>https://flove.org/making-of.html#talk2web-refine_q2</link>
      <guid isPermaLink="false">talk2web-refine_q2</guid>
      <category>Gitea</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Always, automatically — Each recorded interview commits + pushes. Zero drift; matches the current rule.
• On confirmation — Ask before each push. Safer, more friction.
• Manual — You push when you choose.

★ decided: Always, automatically · ◇ recommended: Always, automatically</description>
    </item>
    <item>
      <title>How does 'push' actually post to the commit-wiki (gitea-docsify)?</title>
      <link>https://flove.org/making-of.html#talk2web-refine_q3</link>
      <guid isPermaLink="false">talk2web-refine_q3</guid>
      <category>Gitea</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• docsify-comments via Gitea (Gitalk-style) — Comments land as Gitea issues through a docsify comment plugin; one click, real.
• Gitea API write with a token — Skill writes a wiki page / issue via API. Powerful, needs a stored token.
• Keep copy + open (manual paste) — Current MVP: copy the AI-text, open the page, paste.

★ decided: docsify-comments via Gitea (Gitalk-style) · ◇ recommended: docsify-comments via Gitea (Gitalk-style)</description>
    </item>
    <item>
      <title>DOCS_BASE — where does gitea-docsify actually live?</title>
      <link>https://flove.org/making-of.html#talk2web-refine_q4</link>
      <guid isPermaLink="false">talk2web-refine_q4</guid>
      <category>Gitea</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Gitea on :3000 (wiki render) — Reuse the running Gitea; docsify renders its docs.
• Separate docsify server (own port) — A dedicated docsify instance over the repo files.
• Public docs.flove.org — A published docs host for public deep-links.

★ decided: Gitea on :3000 (wiki render) · ◇ recommended: Gitea on :3000 (wiki render)</description>
    </item>
  </channel>
</rss>
