cross-posted from: https://communick.news/post/7444537

AI Disclosure:

  • Implementation - Hint. Syntax was reviewed and polished by AI.
  • Testing - Assisted. AI was used to troubleshoot whenever I got stuck
  • Documentation - Generated

I spent the last three months slowly tinkering with Headscale and trying to get it to run on one of Google’s “free-tier” cloud instances, while also learning about GCI’s strange setup. During that time I used Claude Sonnet to keep track of my progress and help me troubleshoot whenever I got stuck. I finally got it going and before I closed the project, I asked Claude to document my work along with all pertinent information and create and admin cheatsheet, just in case I forget. I liked the output, so I asked the LLM to sanitize my data and recreate my project as a step-by-step walktrhough in a single HTML page.

PROVIDED AS-IS!!! Do not copy and paste code blindly. Use this as a walkthough/guide and NOT as a recipe book. You WILL need to correct code.

EDIT: It looks like for this document, Claude also took it upon itself to further clean my configs, scripts, etc., and add a lot of comments to make it all easier to understand. I DO NOT work this cleanly. It looks correct though.

  • Helix 🧬@feddit.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 hours ago

    I’m more interested in the way you had Claude document your setup. How did you make sure it didn’t access secrets? Did you copy paste stuff?

    • BadJojoOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 hours ago

      I primarily use LLMs as personal tech writers. I don’t believe in letting it do the work for me because then I’ll lose my skills.

      I start with an outline with all the general steps (1, 2, 3, etc) and feed it to a new Claude chat. I will probably switch to Google Gemini because of its concept of Notebooks. Then as I go along I tell it what step I am working on, what I am doing, and sharr a lot of sanitized copypasta. I leave all internal names and IPs intact but replace external IPs with things like <GCP WAN IP> and <lab WAN IP>. Claude figures it out and replaces it for the sanitized docs. When I am done I ask it to build the full run book with code blocks and it spits out a fully formatted, cataloged (1.1, 1.2, 1.3, etc), spell checked and noted .md file that I can load into Standard Notes or Obsidian. You can also add to the process, vouce notes if you don’t want to type and the LLM will add the text in for you.

        • BadJojoOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          3 hours ago

          PS: If you need a quick way to view Markdown files from any device, you can use this html file. Please host your own copy just in case my neocities page ever goes away. I need to ask Claude to add the viewing options it used on the guide.

          https://smoores.neocities.org/parchment.html

          EDIT: That’s all Claude. I have no HTML skills at all and I just needed a tool.

        • BadJojoOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          3 hours ago

          This is the tech-writer skill I use.

          https://drive.proton.me/urls/ZA9N573TFM#dSc7OnnJnyQ4

          As far as prompts, I just keep them straight forward and clear. Below are the two I used to create the html I shared.

          This is a useful runbook. Recreate this runbook as a guide for public consumption. Output in a single html file. Include codeblocks and diagrams. Fully sanitized of any reference to my internal network, nodes, IPs, etc.

          Good. Please make a version of the html that allows for dark mode, low light lite mode, and high contrast monochrome e-ink mode as selectable viewing options for balanced accessibility.