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.

Sign up for GitHub

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

Jump to bottom

Consider OstreeRef, OstreeConfig, and other models artifactless #256

Open
lubosmj opened this issue May 23, 2023 · 1 comment
Open

Consider OstreeRef, OstreeConfig, and other models artifactless #256

lubosmj opened this issue May 23, 2023 · 1 comment
Labels
Task

Comments

@lubosmj
Copy link
Member

lubosmj commented May 23, 2023 •
edited
Loading

It is not necessary to store the checksum of a commit or a couple of lines for a configuration in a separate file. Use TextField instead.
@lubosmj lubosmj added the Task label May 23, 2023
@lubosmj lubosmj changed the title Make OstreeRef artifactless Make OstreeRef and OstreeConfig artifactless May 29, 2023
@lubosmj lubosmj changed the title Make OstreeRef and OstreeConfig artifactless Consider OstreeRef, OstreeConfig, and other models artifactless May 29, 2023
@lubosmj
Copy link
Member Author

lubosmj commented Sep 4, 2023

This could improve the speed of syncing and importing. Besides that, we will also be able to perform various operations inside repositories more efficiently without accessing the storage backend.

The problem might lie in setting relative paths of remote artifacts. This was the main reason for introducing the models with artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lubosmj