this post was submitted on 15 Feb 2024
39 points (93.3% liked)

Selfhosted

40261 readers
725 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

How to set jellyfin server flatpak to start automaticly when system boots up?

I was doing this earlier wit deb version, but now with flatpak i dont know how to do it.

I installed it via popshop on linux pop os and now i have icon in my apps meny but its anoying to start it manualy every time i restart my pc..

you are viewing a single comment's thread
view the rest of the comments
[–] batman654987@lemmynsfw.com 1 points 9 months ago (2 children)

Isnt docker kind of virtualisation? Is it realy required for this? I would expect flatpak to have a way of autostarting software.. πŸ€”πŸ€·β€β™‚οΈ

[–] richmondez@lemmy.world 8 points 9 months ago

Docker and Flatpack are both containerization technologies and work in similar ways under the hood. Docker is more geared towards running headless services that other systems access while flatpack is more geared towards desktop gui applications that are interacted with from the same system they run on.

[–] gnuplusmatt@reddthat.com 8 points 9 months ago

Docker/podman are not virtualisation, they are containerisation. The system groups all the processes into a namespace and executes them on the same host/kernel as the base system. There is no overhead of virtualisation as its not creating virtual hardware or running a whole OS. Its more like the flatpak you're already running than a vm