A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
[X] Yes, I have searched the existing issues and it doesn't exist.
Feature Description
The CV can now be downloaded as JSON and PDF, but we need to save it ourselves somewhere, such as a drive, local disk, or, in my case, a GitHub repository for version control.
I envision the UI portal having two text boxes: one for the PAT (Personal Access Token) and one for the GitHub repository link. This should be sufficient for pushing the CV. However, we must address security concerns in case this information is leaked. I suggest using symmetric encryption to store the data in a database. When a user requests to push to GitHub, they would be prompted to use the key to decrypt the information. Otherwise, the user would need to regenerate the PAT.
Is there an existing issue for this feature?
Feature Description
The CV can now be downloaded as JSON and PDF, but we need to save it ourselves somewhere, such as a drive, local disk, or, in my case, a GitHub repository for version control.
I envision the UI portal having two text boxes: one for the PAT (Personal Access Token) and one for the GitHub repository link. This should be sufficient for pushing the CV. However, we must address security concerns in case this information is leaked. I suggest using symmetric encryption to store the data in a database. When a user requests to push to GitHub, they would be prompted to use the key to decrypt the information. Otherwise, the user would need to regenerate the PAT.
How do you think about this feature?