Lem453

joined 2 years ago
[–] Lem453@lemmy.ca 3 points 1 year ago (2 children)

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.

[–] Lem453@lemmy.ca 6 points 1 year ago

Bitwarden let's you upload files (key files) and save all you passwords.

[–] Lem453@lemmy.ca 49 points 1 year ago (1 children)

Use aegis, export the keys and then reimport them every time you switch. Trusting your second factor to a cloud is a disaster waiting to happen.

If you want to get fancy setup your own cloud server (nextcloud, Seafile, owncloud etc) and set the backup folder for aegis to the self hosted cloud for easy restore every time you switch ROMs.

[–] Lem453@lemmy.ca 3 points 1 year ago

Ya I'm using the English 79 model (not the default) voice on a pixel 8 and it works very well.

[–] Lem453@lemmy.ca 9 points 1 year ago

If you really want to be pedantic you could setup raid 1+0 or 5 and live the true RAM hot swapping life

[–] Lem453@lemmy.ca 2 points 1 year ago

FWIW collabora and open office can integrate with other clouds like Seafile and owncloud Infinite scale. So even without NextCloud it can be used. It can also be used stand alone.

[–] Lem453@lemmy.ca 1 points 1 year ago

It's not easy but they only way to make it all work without creating massive security holes is to only buy things that allow connection with open standards (which means home Assistant can connect to it.

[–] Lem453@lemmy.ca 5 points 1 year ago (2 children)

The correct way of doing this is to never interact with an iot device directly. Put all of them on the same network with Home Assistant and then control all of them only via Home Assistant. Then you make one exception for home assistant to be accessible to the other networks.

This also allows you to disable Internet access for every single iot device Except home assistant.

[–] Lem453@lemmy.ca 7 points 1 year ago* (last edited 1 year ago)

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.

[–] Lem453@lemmy.ca 9 points 1 year ago (3 children)

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

[–] Lem453@lemmy.ca 1 points 1 year ago (1 children)

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?

[–] Lem453@lemmy.ca 3 points 1 year ago (1 children)

I have no problem supporting devs but locking what should be core features behind a paywall in unacceptable for me.

view more: ‹ prev next ›