snapstore
pbis-open
snapstore | pbis-open | |
---|---|---|
10 | 4 | |
59 | 324 | |
- | - | |
0.0 | 4.1 | |
over 6 years ago | over 2 years ago | |
C | ||
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
snapstore
-
Why does almost all commercial software that chooses to support Linux use Snap instead of flatpak?
- from https://github.com/noise/snapstore/
-
Ubuntu Flavors Decide to Drop Flatpak
the snapstore demonstrated there is no longer in the github repo, or compatible with snapd anymore https://github.com/noise/snapstore
-
Cons of Using snap
The current Snap Store is not open source. The one you referenced is dead as proven by the repo you're article refers to: https://github.com/noise/snapstore/
-
Probono, creator of AppImage, in an attempt to get AppImage support, is banned from the OBS Studio organization on GitHub after downright rude comments and accuses them of supporting Flatpak because of the bounty offered by RH. "In any event, please do not bother our project anymore"
If you're referring to the old HOWTO article for hosting your own snap store server, the software it used to do that stopped working several years ago.
-
Can some one explain to me in basic terms why snaps are so disliked?
That's nice and all, but besides the complete lack of official serversoftware that can be hosted by anyone, I'm going to guess that forcing another URL would mean that it uses that repo INSTEAD OF the official one. With regular package managers and Flatpaks, that's not the case. You can add repo's in ADDITION to the originals with those. The only mention of a self-hostable snap server that I can find, is this one. However, it is an unofficial server and has been depreciated. In other words: it's not compatible/functional with the latest version of Snapd (the clientside) anymore and will remain like that.
- Are flatpaks the future? I tend to agree.
-
snippysnappy
They used to have an example implementation here, though: https://ubuntu.com/blog/howto-host-your-own-snap-store https://github.com/noise/snapstore
-
Is releasing via Snap that bad?
interesting read. unfortunately, the 'snapstore' github project (here) that it links to now says:
-
After 1.5 years of using Ubuntu I decided to migrate to Fedora today... so yeah, hello world!
Your link is an blogpost from 2016 that points to: https://github.com/noise/snapstore README: snapstore was a minimalist example of a "store" for snaps, but is not compatible with the current snapd implementation. As a result I have removed the contents here to avoid further confusion.
-
Ubuntu 21.04 Released
In fact, Bret Barker has published an open source (Apache License) SNAP store on GitHub. We’re already looking at how to flesh out his proof-of-concept and bring it into snapcore itself.
https://github.com/noise/snapstore/
pbis-open
-
PBIS-Open is archived and no longer maintained, alternatives?
Alright, so there's a lot of folks that are really happy joining Linux machines to AD Domains with https://github.com/BeyondTrust/pbis-open --- and up till kinda recently, that was a really reliable, viable way of allowing linux servers in a primarily Windows environment to benefit from AD Domain Login, including things like restricting login to certain groups, etc. From a higher-ed perspective, where the vast majority of systems (at least endpoints) are Windows and rely on AD for SSO login, this seems like an ideal solution.
- Linux Servers in AD domain
- Linux and active directory integration/joining domain?
-
Ubuntu 21.04 Released
I would say the same but for authentication.
We have linux servers on our domain, specifically becaeuse there are certain things they do better than windows, and im a tool for a trade kinda guy.
But authentication and management of creds is a hard requirement.
The rest i can work with. We setup Ansible to handle much of the day to day config things. GPO"s might be nice.
At one and for years i was using PBIS, and whatever it was called before it was bought out, forked and named PBIS - https://github.com/BeyondTrust/pbis-open
I liked it because it kept GID/UID's consistent across the domain. But it was flaky for samba shares specifically ad group enumeration. There are paid add-ons that leverage GPO but never went that route.
More recently we are just leveraging SSSD/Chrony/Smb/Nmb to do the same, there are a few tweaks, but its solid. Its actually more stable now.
Some GPO's would be nice I supposed.
What are some alternatives?
Flatseal - Manage Flatpak permissions
ubuntu-desktop-installer - Ubuntu Desktop Installer
pipewire - Mirror of the PipeWire repository (see https://gitlab.freedesktop.org/pipewire/pipewire/)
snapcraft - Package, distribute, and update any app for Linux and IoT.
flatpak - Linux application sandboxing and distribution framework
shared-modules - Common Flatpak modules that can be used as a git submodule
dash-to-dock - A dock for the Gnome Shell. This extension moves the dash out of the overview transforming it in a dock for an easier launching of applications and a faster switching between windows and desktops.
rustdesk - An open-source remote desktop, and alternative to TeamViewer.
appimage-builder - GNU/Linux packaging solution using the AppImage format
AppImageLauncher - Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages
mir - The Mir compositor