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.

  • BadJojoOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    4 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.