.env are super annoying to backup and recreate on new install. Could be solved with a simple snapshotter:
snapshot-env capture . ~/Dropbox would detect all .env files nested in the provided folder (default = current one), copy them and also keep in memory their position. Ideally, it would generate a file containing the ".env " files + their location (since they are text file we could shove that into a single big yaml file or similar). Ideally it ignores files tracked by git (how to tell that?). Then it stores the snapshot into the provided folder (default = current folder, in this example I use dropbox).
snapshot-env restore ~/Dropbox/my-env-file.env . restores the snasphot file into the current directory
Actually this could generalize to all untracked files, except generated ones/node_modules. We could use a threshold to keep only files that are not too big.
.env are super annoying to backup and recreate on new install. Could be solved with a simple snapshotter:
snapshot-env capture . ~/Dropbox
would detect all.env
files nested in the provided folder (default = current one), copy them and also keep in memory their position. Ideally, it would generate a file containing the ".env " files + their location (since they are text file we could shove that into a single big yaml file or similar). Ideally it ignores files tracked by git (how to tell that?). Then it stores the snapshot into the provided folder (default = current folder, in this example I use dropbox).snapshot-env restore ~/Dropbox/my-env-file.env .
restores the snasphot file into the current directoryActually this could generalize to all untracked files, except generated ones/node_modules. We could use a threshold to keep only files that are not too big.