AaronV77 / Monday

Scripts that create aliases in order to be able to push and pull from a central storage server that you can have at home.
GNU General Public License v2.0
0 stars 0 forks source link

Multiple Storage Locations #26

Closed AaronV77 closed 5 years ago

AaronV77 commented 5 years ago

If there is more than one location for storing. I don't want the user to have to consistently keep including the new location every time a push or pull command is called. If the user could just provide it once, then I feel like that would be sufficient and for the scripts to have a way of collecting all the different locations.

What I'm thinking is that there is a folder in the main home directory. This could be the living place of where the scripts are stored. I would include a hidden file that stores all of the locations in it and sets which one is currently active. Note We could then get rid of the credential scan because we would then not include the hidden file in the package.

We should also have a different setup feature for developers or just users. The one for developers would setup the directory with an update script (would use the credential script, update the aliases if needed, and put the updated scripts into the git directory), and all of the other scripts including test. Then for all other users, then just the push and pull script.