the gmail credentials will need to fetched from the user on first cli run or on auth command. when doing so, the credentials need to be securely stored on the client device. that means we need to password encrypt. the password is not stored, only the user knows it. this means we can safely hash using the password as a seed and store the hash in a file. the location of this secure file needs to be pointed to by the config key :gmail-credentials-path.
since we are using aero, the path to the credentials is the only config that we have. the file may or may not exist, this needs to be taken into account. it is then also possible to make the file be an environment variable defined in the aero config. so that a user could override the location of the gmail credentials on their system using a shell variable before running the cli.
the gmail credentials will need to fetched from the user on first cli run or on auth command. when doing so, the credentials need to be securely stored on the client device. that means we need to password encrypt. the password is not stored, only the user knows it. this means we can safely hash using the password as a seed and store the hash in a file. the location of this secure file needs to be pointed to by the config key :gmail-credentials-path.
since we are using aero, the path to the credentials is the only config that we have. the file may or may not exist, this needs to be taken into account. it is then also possible to make the file be an environment variable defined in the aero config. so that a user could override the location of the gmail credentials on their system using a shell variable before running the cli.