.splitIgnore Method to Update from src VSCodiumVM

Im wondering if it would be possible to have a setup like this for code projects…

[proxyUSBVM] Air Gap Storage
Encrypted USB storage
Holds - Trusted & Important Code Files, Split Instructions

[srcIDEVM-dvm]: Large Files & Dev
VSCodium or Other IDE (which would be a clone of default [devIDEVMxxxx] )
Holds - Trusted IDE App, Project Files and Dependencies, Desktop/Windows Configuration.
Does Not Hold - Trusted & Important Code Files such as ( .env, main code files etc)

[devIDEVMxxxx] Numbered Disposable
Starts with App and Data from [srcIDEVM-dvm]:
Ingests and Merges Split Instructions and Data from [proxyUSBVM]
Main coding dev workstation.
Either tests somehow for trustfulness of libs and modules or sends to another qube for testing
Adds Trusted and important files at end of dev session to .splitIgnore list
Updates/Pushes new files to [srcIDEVM-dvm]: & [proxyUSBVM] with versioning applied.

Heres a completely barbaric attempt at a flow chart
:triumph:

 ⊞ # From [devIDEVMxxxx] Numbered Disposable
 β”‚
 β–Ό
[proxyUSBVM] # Airgap Storage 
    # Project Docs's
    splitREADME.md & .splitIgnore 
    README.md & .gitignore 
    └── Overall project splitting explation and versioning documentation
        β”‚
        β”œβ”€β”€[proxyUSBVM]
        β”‚       β”œβ”€β”€ Src files, .env's, config.json's, styles.css 
        β”‚       β”‚   └── Small Files and folders to include in split
        β”‚       β”‚       for secure air gapped storage anything thats valuable as ip
        β–Ό       β–Ό
        β”‚       β”‚
        #       # Copied into numbered disposable
        β”‚       β”‚
        β–Ό       β–Ό
β”Œ--β–Ί[devIDEVMxxxx] # Numbered Disposable
β”‚       β”‚
β”‚       Ingests Small Files [proxyUSBVM] # Project Docs's, Trusted & Important 
β”‚       Ingests stored data [srcIDEVM-dvm] # Trusted
β–²       └── Coding is performed, Testing and New Module/Lib Trusfulness Assessed
β”‚           └── Split is performed based on splitREADME.md & .splitIgnore 
β”‚                        β”Œβ”΄β”
β”‚           Large Files β”€β”˜ └─ Small Files 
β”‚           β”‚                 β–Ό          
β”‚      β”Œβ”€β”€β”€β”€β”˜                 β”‚        
β”‚      β”‚                      ⊞ To [proxyUSBVM] Airgap Storage
β–²      β–Ό
[srcIDEVM-dvm] # Large Files & Dev
    Takes instruction [devIDEVMxxxx] # Project Docs's 
    Ingests ignored data [devIDEVMxxxx]  stores in VM for next dev session
        β”‚
        └── React/Node.js Components
    	      └── Large Files and folders to ignore in split
                  stays in srcIDEVM-dvm

:thinking:
I think have kind of answered my own question here (of how to go about this),

But any input or tips to set this up with simple scripts to automate the splitting and ingesting would be a huge help. Im still a forevern00b…

I would like to be able to plugin a usb decrypt in a non-net capable dispvm, start up a new numbered disposable IDE app instance, securely send a folder from the USB to the disp, then in the disp hit alt-F2 and type ingest and it automatically populates the working folder(already in disp as its based on the dvm which has the Large Files) with the folder from the usb.

I think i may be complicating this waaay too much and maybe a simple .splitIgnore file and a copy to usbvm script could do it?

Any thoughts or discussion would be much appreciated.

Sorry for the non sequitur, but what did you use to create that flowchart? Looks pretty cool.

2 Likes

its a piece of software i wrote