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

RFC: support non-flatpak repositories #37

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

abderrahim
Copy link
Contributor

We were discussing the possibility of maintaining non-flatpak ostree repositories using flat-manager. This is a quick and dirty "what does it take to make it work?" hack.

In fact, not much. flatpak build-commit-from seems to cope well with non flatpak refs, except that they need to be specified explicitly on the command line. The other change is removing the check for invalid refs.

I guess endless people may be interested too, but I'm not sure who to ping.

CC: @barthalion @valentindavid

@@ -293,7 +293,7 @@ fn validate_ref (ref_name: &String, req: &HttpRequest) -> Result<(),ApiError>
}
req.has_token_prefix(ref_parts[1])
},
_ => Err(ApiError::BadRequest(format!("Invalid ref_name {}", ref_name))),
_ => Ok(()), // Err(ApiError::BadRequest(format!("Invalid ref_name {}", ref_name))),
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think rather than completely removing the check, it would be better to add a configuration option to disable it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or maybe make it non-fatal, but still logged?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think allowing any refs at all is a good idea. Clients can then e.g. replace appstream/x86_64 or other internal "trusted" refs. Allowing some prefix seems better.

@ieugen
Copy link

ieugen commented Jun 3, 2020

Hi, I would love this option. I'm looking for a way to distribute CLI apps and SDK in a fashion similar to how sdkman.io and node version manager https://github.com/nvm-sh/nvm operate.

I'm thinking of doing this like flatpak but without sandboxing since CLI apps are hard to configure for sandboxing.

IMO having this option will expose more people to ostree and flatpak style of building apps and help with the migration. Also it will be exploratory for how CLI apps can be sandboxed more or isolated.

I also believe that having developer tools distributed with this tech will expose more developers and increase adoption.

Looking forward to any news about this feature.

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

Successfully merging this pull request may close these issues.

4 participants