Closed MrADevelopers closed 4 years ago
Thanks Sir! Yes I am aware of this issue, we are working toward resolving it! If you find any other issues let me know! Let's keep the issue open until it isn't solved!
Great! By the way good work.
I have one more question, is there any way to move .kb file in C://Users/user name/.kb to any other drive or location since if the windows get corrupted for any reason all the data will be lost ?
@MrADevelopers Thanks for your appreciation!
For what concerns the corruption of data, I have some words about it.
1 - We are working on a synchronization infrastructure that will be git-based, unluckily for this you should wait for version 0.2
2 - At the moment I suggest you frequently do:
kb export
or if you only want to export raw data:
kb export --data
So do it frequently and backup, then you can import the package exported by kb export
back by doing:
kb import
Another note about why I designed the kb export --data
.
I added this option, since I thought that some user would like to export the raw data organized by categories as an archive, so
that you could:
1 - use (or import) this data with other software related to knowledge management
2 - restart from scratch with kb if the database in some way is corrupted, in this case, if you only have the data archive organized by directories you can do this:
Let's say you had three categories in kb, hence you will have three directories in the data archive (e.g., default, cheatsheet, theory) now you can import your data back by doing:
kb add path/to/default/ --category "default"
kb add path/to/cheatsheet/ --category "cheatsheet"
kb add path/to/theory/* --category "theory"
I hope that is clear!
Thank you! appreciate your clarifications
Another note about why I designed the
kb export --data
. I added this option, since I thought that some user would like to export the raw data organized by categories as an archive, so that you could: 1 - use (or import) this data with other software related to knowledge management 2 - restart from scratch with kb if the database in some way is corrupted, in this case, if you only have the data archive organized by directories you can do this: Let's say you had three categories in kb, hence you will have three directories in the data archive (e.g., default, cheatsheet, theory) now you can import your data back by doing: kb add path/to/default/ --category "default" kb add path/to/cheatsheet/ --category "cheatsheet" kb add path/to/theory/* --category "theory" I hope that is clear!
Cool, I used to write an issues blog based on GitHub Actions gitblog--In Chinese,
I think I can combine issues and issues comments with your wonderful work -- kb
like using Python
log
issue label is category and comment is one new kb
, when issue or issue comment add, the GitHub action trigger, add it too kb, then export to file add auto commit.
Using that I can auto share my kb on GitHub, and grep in my local cmd.
@yihong0618 thanks Sir, and thanks a lot for your valuable help!
And pls share the installation directory of the project so I can have a loot at the source too.
Sorry ? What do you mean by the installation directory of the project ? You mean where artifacts are saved? Look into $HOME/.kb/
No where the source code of the KB is, that handles all the commands etc.
The source code is on github you can get it by doing: git clone https://github.com/gnebbia/kb
Yeah but i want to know where it sits on my PC
Well this depends on your configuration, are you installing it with pip? do you have pyenv? are you using python from the app store or downloaded online? Are you using the git repo? It really depends on how you installed kb.
i installed it from pip, i installed python from internet (sorry i am not good at python)
It also depends on you python version then, I would suggest to use git and github to tinker with code!
This bug has been fixed! Update kb with git and everything will work!
Another note about why I designed the
kb export --data
. I added this option, since I thought that some user would like to export the raw data organized by categories as an archive, so that you could: 1 - use (or import) this data with other software related to knowledge management 2 - restart from scratch with kb if the database in some way is corrupted, in this case, if you only have the data archive organized by directories you can do this: Let's say you had three categories in kb, hence you will have three directories in the data archive (e.g., default, cheatsheet, theory) now you can import your data back by doing: kb add path/to/default/ --category "default" kb add path/to/cheatsheet/ --category "cheatsheet" kb add path/to/theory/* --category "theory" I hope that is clear!Cool, I used to write an issues blog based on GitHub Actions gitblog--In Chinese, I think I can combine issues and issues comments with your wonderful work --
kb
like using Python logissue label is category and comment is one new
kb
, when issue or issue comment add, the GitHub action trigger, add it too kb, then export to file add auto commit.Using that I can auto share my kb on GitHub, and grep in my local cmd.
@gnebbia
Done! I combine the two system~ with GItHub Actions
Thank you for your great work!
That's cool! I am happy to hear that! And again thanks for your contributions and helping me finding and solving bugs!
I am using windows 8.1 every thing seems to work fine its an excellent work. Just one problem, when i use this command kb view -i 0 -e
it says permission denied error13