• 15 Posts
  • 699 Comments
Joined 11 months ago
cake
Cake day: August 25th, 2025

help-circle










  • I’m doing some training stuff for work thats eating up my week, but I’ll help work through that with you later on if you’d like

    The wiki itself is a slightly different bit, its the repo with .wiki at the end and it is its own thing (one of the oddities of codeberg wiki I mentioned)

    You can also comment here or send me a message, or write it in your fork and let me know, whichever works. I don’t believe there is anything that I’d consider “uninteresting input” fwiw :)






  • So I’m going to suggest something slightly different - put it on both github and codeberg, then note that its synced from your local repo as a mirror and link it in a readme.

    Gives you a few things

    • Readily accessible and fast options for the recruiter to access, even if your power is out / motherboard blows up / whatever.
    • Demonstrates your familiarity with a world beyond github
    • Demonstrates you can stand up your own local repo (if this is a thing they care about - if not don’t bother with your own repo for just this)

    As for the server itself I’d say forgejo personally.





  • Why would you?

    The important part is your VMs and LXCs. Your Proxmox server, at most, requires configuration for specific needs (GPU passthrough for example). The only thing you need for that would be notes on configuration (unless you have this automated, in which case you don’t generally need that, just the notes in your scripts).

    So a more important question, to me, is why do you want to back it up in the first place?