Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use relative paths in .tufup-repo-config #50

Closed
dennisvang opened this issue Sep 30, 2022 · 2 comments · Fixed by #78
Closed

Use relative paths in .tufup-repo-config #50

dennisvang opened this issue Sep 30, 2022 · 2 comments · Fixed by #78
Assignees
Labels
enhancement New feature or request

Comments

@dennisvang
Copy link
Owner

dennisvang commented Sep 30, 2022

Background

The .tufup-repo-config file, that is created when initializing a repository, includes absolute paths for the keys_dir and repo_dir.

Although these can easily be modified, when necessary, the file should be portable out-of-the-box.

Proposal

It would be more convenient to use relative paths in the .tufup-repo-config file. That is, relative to the config file location.

@dennisvang dennisvang added the enhancement New feature or request label Sep 30, 2022
@dennisvang dennisvang self-assigned this Sep 30, 2022
@wickeat
Copy link

wickeat commented Sep 5, 2023

This enhancement would be great in making the implementation portable across different environments! Currently, I am manually editing the keys_dir and repo_dir of the .tufup-repo-config file.

@dennisvang
Copy link
Owner Author

dennisvang commented Sep 6, 2023

@wickeat This was a bit tougher than expected. Perhaps you could have a look at #78 to see if the proposed solution would work for your case?

For testing you could do a vcs install, directly from github, e.g.

pip install tufup@git+https://github.com/dennisvang/tufup.git@issue50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants