| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| btnmkey [2025/07/09 20:35] – admin | btnmkey [2025/07/09 20:41] (current) – admin |
|---|
| **NOTE:** Make sure such a member is registered at the server for your //Git Winch// or if the member was not registered then that person must quickly register there before the said person can be regarded as a member. | **NOTE:** Make sure such a member is registered at the server for your //Git Winch// or if the member was not registered then that person must quickly register there before the said person can be regarded as a member. |
| |
| This functionality is the only one on this page which can actually be created by anyone. The button for creating Deploy Keys behaves in two ways: | |
| | ====Important==== |
| | Every member should ALWAYS take care that the member's own //.priv// key for each and every repository they work on exist on their own computer. The keys must be kept in the //members// folder within the application folder of //Git Winch// present on their own computer. |
| | |
| | |
| | This functionality is the only one on the //manage// page of //Git Winch// which can actually be used by anyone. The button for creating Deploy Keys behaves in two ways: |
| |
| **If you are an ordinary member or manager:**\\ | **If you are an ordinary member or manager:**\\ |
| |
| **Creating a member's own Deploy key by the Manager/owner is not recommended**\\ | **Creating a member's own Deploy key by the Manager/owner is not recommended**\\ |
| As explained earlier, it is not a good idea to share the member's private key with anyone else other than the member himself/herself. But in some cases, a member may not be knowing how to... and hence we gave the functionality to mamanger/owner to generate the Deploy Keys on behalf of the member. | As explained earlier, it is not a good idea to share the member's private key with anyone else other than the member himself/herself. But in some cases, a member may not be knowing how to... and hence we gave the functionality to manager/owner to generate the Deploy Keys on behalf of the member. |
| | |
| | Hence ideally; a remote worker may want to create his/her own Deploy keys. |
| |
| **Where are the Deploy Keys kept ... and other details:** | **Where are the Deploy Keys kept ... and other details:**\\ |
| For example; a remote worker may want to create his/her own keys button. After the keys are generated, the person should locate the generated key in the //members// sub-folder within this application's folder. The name of the newly created key filenames would be of this format: | After the keys are generated, the person should locate the generated key files in the //members// sub-folder within this application's folder. The name of the newly created key filenames would be of this format: |
| |
| <repositoryname>_<membername>.pub\\ | <repositoryname>_<membername>.pub\\ |
| The member (Rekha) can then send the file //ourofficework_Rekha.pub// to the actual owner of the //ourofficework// repository with the request that the member be added to the group of the //ourofficework// repository. As stated above, Rekha should ideally never ever share the private key. | The member (Rekha) can then send the file //ourofficework_Rekha.pub// to the actual owner of the //ourofficework// repository with the request that the member be added to the group of the //ourofficework// repository. As stated above, Rekha should ideally never ever share the private key. |
| |
| But as a convenience, the manager/owner can also create the member (Rekha) key pairs (explained earlier). In that case, ideally, the manager/owner must first send the //.priv// file to the member (Rekha) and delete it from their own computer. Rekha; the member, should take care that the said //.priv// key must be kept in the //members// folder within the application folder of //Git Winch.// | As a convenience, the manager/owner can also create the member (Rekha) key pairs (explained earlier). In that case, ideally, the manager/owner must first send the //.priv// file to the member and delete it from their own computer. |
| |
| ----- | ----- |
| [[/concepts?do=export_xhtml | Learn the concepts]] | [[/topics?do=export_xhtml | Table of Contents]] | [[/concepts?do=export_xhtml | Learn the concepts]] | [[/topics?do=export_xhtml | Table of Contents]] |
| |