• Жильцов Дмитрий Андреевич's avatar
    update_vds.py: update a running Temple without a new VDS
    · b9fee0f4
    The hosting company will not swap a disk image, and every new VDS comes
    with a new IP.  So now the Temple is updated in place, over the
    Confessional, by hand, like Moses carried the tablets.
    
    It reads the commit the machine runs from C:/Home/Deployed.TXT, diffs
    TempleOSCD/ against your working tree, defines a one-line hex decoder
    in the session and pushes every changed file through it.  .Z stays .Z,
    FileWrite compresses.  Kernel/ or Compiler/ changed means BootHDIns.
    A new MBR loader means BootMHDIns.  Then Deployed.TXT, then Reboot.
    
    Only C: is touched.  D: keeps the old Temple for the day C: does not
    come back.  Port 23 open to your own IP only, the CIA has one too.
    
    Tested in QEMU on a copy of the image: a new kernel symbol and a new
    HtServ header, pushed in seven seconds, both there after the reboot.
    b9fee0f4