What is the right way to install snap on Fedora
-
@brandon220 said in What is the right way to install snap on Fedora:
Makes perfect sense.
For reference: https://mangolassi.it/post/431462
-
@brandon220 said in What is the right way to install snap on Fedora:
What snap applications would one normally run instead of installing the traditional way? Are there worries about them being insecure? For instance - I saw there is a Nextcloud snap. Would you ever consider using it?
No, Snaps for server services of any complexity (like needing to configure a database or cache) is highly problematic. Snaps work best for desktop apps and similar things. The "needs" of the application are very different.
We DO use Snaps for Rocket.chat as no configuration is really needed.
-
@JaredBusch yeah, the fonts in the Snap are awful.
-
We DO use Snaps for Rocket.chat as no configuration is really needed.
The other issue with Snaps is that they often fall behind the main release stream. Rocket.Chat is a prime example of this. Current Snap is 0.72.3 and the rpm/deb release is at 0.73.2.
-
@manxam said in What is the right way to install snap on Fedora:
We DO use Snaps for Rocket.chat as no configuration is really needed.
The other issue with Snaps is that they often fall behind the main release stream. Rocket.Chat is a prime example of this. Current Snap is 0.72.3 and the rpm/deb release is at 0.73.2.
Well snaps are just containers, which contain just that application. So if the snap developer hasn't updated it for any reason you wouldn't have the most current release.
Same kind of issue exists with Chocolatey (on Windows) were the software developer will create an updated version. But the chocolatey repo isn't updated.
So either you wait or you upgrade and leave Chocolatey installation behind.
-
@DustinB3403 said in What is the right way to install snap on Fedora:
@manxam said in What is the right way to install snap on Fedora:
We DO use Snaps for Rocket.chat as no configuration is really needed.
The other issue with Snaps is that they often fall behind the main release stream. Rocket.Chat is a prime example of this. Current Snap is 0.72.3 and the rpm/deb release is at 0.73.2.
Well snaps are just containers, which contain just that application. So if the snap developer hasn't updated it for any reason you wouldn't have the most current release.
Same kind of issue exists with Chocolatey (on Windows) were the software developer will create an updated version. But the chocolatey repo isn't updated.
So either you wait or you upgrade and leave Chocolatey installation behind.
The issue is not unique to snap or chocolately or anything.
The issue is with the developers. That is why I always aim for the targeted deployment method if there is one that matters.
If the devs update the repo most, go that route. if they do snap, or docker or WTF ever, go that route.
-
@JaredBusch said in What is the right way to install snap on Fedora:
The issue is with the developers. That is why I always aim for the targeted deployment method if there is one that matters.
For the record there is no one specified "preferred method" that I can see form the OnlyOffice website. Repo and Snap are treated equal.
I tried repo first and it failed in November. So I tried Snap. It always had these SELinux issues, but I ignored it as I was only testing.
-
@JaredBusch will you be willing to write up a guide for getting open office working with NC, specifically behind nginx? I can try and fumble through it, but you make things look so easy.
-
@Donahue said in What is the right way to install snap on Fedora:
@JaredBusch will you be willing to write up a guide for getting open office working with NC, specifically behind nginx? I can try and fumble through it, but you make things look so easy.
I've never set it up. I can try.
-
@Donahue said in What is the right way to install snap on Fedora:
@JaredBusch will you be willing to write up a guide for getting open office working with NC, specifically behind nginx? I can try and fumble through it, but you make things look so easy.
@romo and I have that working. That's how ours works. Romo had to modify the Docker instance because the instance itself is misconfigured for doing this.
