New features and improvements
OrkoHunter opened this issue · 15 comments
- keep pull replaces the existing commands with new one. The default option should be to update not replace while replace being available as an option to the user
- Use shell history to save commands #3
- keep rm
- Give option of giving password input while registering an existing user
- Outdated warning while using
- keep run should be more interactive
- Don't execute pull if never pushed on server.
From experience with a similar workflow, but using a text file in a cloud drive:
You want to have some option to sort/move or have a hierarchy. If you have to look for your command by reading hundred(s) lines, you are back at square one. Something like Hierarchical Notebook maybe for ideas?
Nice start app :) I need this!
- it would be nice if command line autocomplete for commands and dir/file names was implemented. I think readline is one way of doing this very cheaply.
- ++1 for use shell history to save commands! readline again?
- If my analysis is correct, the remote database/server for push/pull is your heroku space.
A large warning to beginners about not storing commands with secrets on your server would be nice.
Even nicer would be an option to allow me to install the server code wherever I like.
I assume the server is basically just a simple authenticate -> store json object -> return or authenticate -> return json object. Where is the server source code? Sorry if I missed it in this repository :}
@OrkoHunter - Thanks for that :)
I <3 to keep things on cloud (backups, files, etc.) and It's nice I can have now commands. I'm just waiting to support for password or even an e-mail recovery option for lost credentials.
How about adding commands with placeholders?
If I want to execute grep -irnw /path/to/dir -e pattern I want to save it in a way that
will allow me to edit those parameters before executing.
Maybe 'Keep' will save it like this: grep -irnw $dir -e $pattern and when running this command
'Keep' will ask me for those parameters or allow me to send then as options to the command, something like: keep run ... --dir /path/to/dir --pattern pattern
@paci4416 Few days ago, I wished for the exact same thing while extracting an archive. Thanks very much for the input! I can't work on it soon, but will do it once available.
Can you put up a CONTRIBUTE.md?
I am new to python development and would like to commit to this repository.
@OrkoHunter Loved the idea! How about adding support for scripts as well? For eg, I have around 10 commands I execute to mount all 3 of my drives (fixing ntfs, mount etc). So something on the lines of a 'keep new --script [Location to the script]'. A copy of this script is not stored in the same place as as 'credentials.json' or wherever and can be executed from keep in the same way.
What do you think?
@OrkoHunter Is there a way you can implement a feature that allows you to remove a command by specifying a number to each command because I stored a command that has very rare characters which are not on my keyboard [was a mistake]. So when I try to remove it the cmd does not understand the command to remove.
@olaoluwa-98 Can you try
keep update
to confirm that you have the latest version? keep rm "some string in command/description" now allows you to choose and remove. Generous courtesy to @paci4416 :)
@OrkoHunter thank you, I realized my version is 2.1.3. I have updated it and it works as described
Glad to know!
I would like to see a way to categorize different commands. As an example, I have some bash commands, I have some AZ Cli commands and I have some vault cli commands. If there was a way to Label, that would be cool
It would be nice,if we have option to choose where to run command. Like in shell or in subshell.
It will be helpful for environment related commands. Like souce,export.