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

Suggested content #58

Closed
matthiasclasen opened this issue Jun 2, 2016 · 4 comments
Closed

Suggested content #58

matthiasclasen opened this issue Jun 2, 2016 · 4 comments

Comments

@matthiasclasen
Copy link
Contributor

Here are some questions that I think might be good to answer, either on the website itself, or as an faq:

  • Can flatpak be used for servers too ?
  • How does flatpak compare to other application sandboxing technologies: zeroinstall, glick, snap, ... ?
  • How does flatpak compare to other packaging technologies: rpm, dep,... ?
  • Which runtime should I use for my app ?
  • What about security updates ?
@jimmac
Copy link
Contributor

jimmac commented Jun 2, 2016

FAQ sounds appropriate, but perhaps security updates (frequent argument for distros) is an area we should emphasize. If we have a good story there, that is :)

@alexlarsson
Copy link
Member

Can flatpak be used for servers too ?

Flatpak is designed to run inside a desktop session, and relies on certain session services being there, such as a dbus session bus and a systemd --user instance. So, is not a good match for a server.

However, the build features of flatpak run fine outside a session, so you can build things on a server.

How does flatpak compare to other application sandboxing technologies: zeroinstall, glick, snap, ... ?

This is complicated to answer. I'm not sure we want to go through the pain of doing comparison to all of these.

jimmac added a commit that referenced this issue Jun 2, 2016
@allanday
Copy link
Collaborator

allanday commented Feb 2, 2017

"Which runtime should I use for my app ?" is covered by the updated runtime page - http://flatpak.org/runtimes.html

@allanday
Copy link
Collaborator

I've created issue #227 and #228 to track the remaining parts of this.

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

No branches or pull requests

4 participants