Quote:main.go is our main runtime.
files.go finds all files in cwd and subdirs
gui.go - this is the interface where they would need to enter license. if they enter it, it unlocks any files in same dir / subdirs/files too.
cli.go - uses shared functions, for command line access to encrypt/decrypt
encrypt.go - handles secure encryption/decryption
config.json - stores plaintext license key (pre-build only), and GUI settings
build.sh - compiles program w/ config settings

we are deploying env/vms for customers, and we give them access to system but they must enter license key to access files & use. what we do is spin up a vm, then run our main program which locks all files/folders (encrypt) until they enter key (in .txt file, should not be read in runtime, instead the build process must use it and store in program using a hash - but not in plaintext because its a license key!)

We run this on our secure vm, it locks down the filesystem to encrypt all files (not itself) in same cwd as the program is actually located/running, and subfolders/files recursively.