This is the correct answer for the selfhosted crowd
This is the correct answer for the selfhosted crowd
Sleep mode seems to be working well for me on fedora atomic with kde (aurora).
Deep sleep works well and can stay sleeping for days.
Normally sleep rules are working well. The do not sleep toggle in the power menu also works to prevent it from sleeping.
Only thing that doesn’t work is flatpak apps can’t prevent the system from sleeping, so watching a video, using Handbrake to encode etc will all just allow it to sleep if there is no physical input.
I have a 2018 dell xps
And borgmatic makes retention rules with automatic runs super easy. It basically a wrapper that runs borg on the client side.
I’ve been using this for a few months now. Its really great.
Last in checked, there is an open PR for the PWA Android app the expose the share function. That will allow this to work however you will have to install the PWA via chrome since the share feature for PWA is proprietary. Sucks because I use Firefox with a bunch of privacy features .
Https is end to end encryption and doesn’t need to be on their road map
Encryption at rest could be an option but seeing as how many other projects have trouble with it (nsxtcloud), its probably best to have this at the fike system level with disc encryption
Same with jellyfin.
They basically don’t accept recurrent donations on purpose
I’ve got multiple apps using LDAP, oauth, and proxy on authentik, I’ve not had this happen.
I also use traefik as reverse proxy.
I didn’t manually create an outpost. Not sure what advantage there is unless you have a huge organization and run multiple redundant containers. Regardless there might be some bug here because I otherwise have the same setup as you.
I would definitely try uploading everything to the latest container version first
For people wanting the a very versatile setup, follow this video:
Apps that are accessed outside the network (jellyfin) are jellyfin.domain.com
Apps that are internal only (vaultwarden) or via wireguard as extra security: Vaultwarden.local.domain.com
Add on Authentik to get single sign on. Apps like sonarr that don’t have good security can be put behind a proxy auth and also only accessed locally or over wireguard.
Apps that have oAuth integration (seafile etc) get single sign on as well at Seafile.domain.com (make this external so you can do share links with others, same for immich etc).
With this setup you will be super versatile and can expand to any apps you could every want in the future.
Does anyone know if dockge allows you to directly connect to a git repo to pull compose files?
This is what I like most about portainer. I work in the compose files from an IDE and the check them into my self hosted git repo.
Then on portainer, the stack is connected to the repo so only press a button to pull the latest compose and there is a check box to decide if I want the docker image to update or not.
Works really well and makes it very easy to roll back if needed.
Bitwarden let’s you upload files (key files) and save all you passwords.
I don’t remember all the details. They never went closed source, there was a difference in opinion between primary devs on the direction the project should take.
Its possible that was related to corporate funding but I don’t know that.
Regardless it was a fork where some devs stayed with owncloud and most went with NextCloud. I moved to NextCloud at this time as well.
OwnCloud now seems to have the resources to completely rewrite it from the ground up which seems like a great thing.
If the devs have a disagreement again then the code can just be forked again AFAIK just like any other open source project.
If I understand it correctly, layering an application is no more dangerous than a regular install on a non atomic os. In other words, every piece of software you have installed on normal fedora desktop is not containerized, if it’s software you were going to install anyways, layering it is the same as before (albeit significantly slower than install and update).
But that means that you get great benefits because 99% of your software packages are properly containerized
I only read the beginning but it says you can use it for private deployments but can’t use it commercially. Seems reasonable. Any specific issues?
I have no problem supporting devs but locking what should be core features behind a paywall in unacceptable for me.
I mean software that’s actively being developed can’t be called DOA. Even if it’s garbage now (and I don’t know if it is) doesn’t mean it can’t become useful at a future date.
Its not like a TV show where once released it can never be changed.
Oh never mind, I saw this finding announcement for 6M and assumed it was the same company. Looks like they have many corporate investors…doesn’t inspire too much confidence.
Although they are still using the Apache 2 license and you can see they are very active in github. It does look like it’s a good FOSS project from the surface.
Ya it was bought by kiteworks which provides document management services for corps (which explains why that mention traceable file access in their features a lot).
That being said, they bought them in 2014 it seems and it’s been a decade now
Correcting: they were bought very recently, they have been accepting corporate funding for more than a decade however. That’s not bad in and of itself.
Thank your for providing first hand perspective. I’ll probably try to spin up a docker deployment for testing.
I don’t really plan to use many of the plugins since I think that was the down fall of NextCloud. Trying to do everything instead of doing it’s core job well.
Is it still a drop in replacement for gitea, I’ve been meaning to switch