Dust0741

joined 2 years ago
[–] Dust0741@lemmy.world 3 points 7 hours ago

Not sure, but if LineageOS supports it, that should be all you need

[–] Dust0741@lemmy.world 10 points 14 hours ago (3 children)

Early alpha, but yea it's full on Linux in Android. Quite slick

[–] Dust0741@lemmy.world 2 points 14 hours ago

I don't know. I think they are pretty good at managing battery, and have a new setting for maxing it out at 80% charge, but I don't think I'd put it near anything expensive for years on end.

[–] Dust0741@lemmy.world 6 points 15 hours ago (3 children)

Yea kinda. Android is switching to quarterly releases, so my phone now says "Android 15" but this was QPR2 specifically

[–] Dust0741@lemmy.world 4 points 17 hours ago* (last edited 15 hours ago) (1 children)

Hmm I was messing with its networking. External vpns break stuff on GrapheneOS. Its internal IP was 192.168.0.2, and my network is different.

[–] Dust0741@lemmy.world 3 points 20 hours ago

https://docs.docker.com/engine/install/debian/#install-using-the-repository

That's it lol. To turn on the terminal, it's a developer option for now, and is very alpha, just search for Linux in settings after turning on dev mode

[–] Dust0741@lemmy.world 25 points 20 hours ago (1 children)

That's Debian in the screenshot

[–] Dust0741@lemmy.world 12 points 20 hours ago

Oh man that'd be super cool. An ARM cluster of androids would be awesome. Battery backups built in!

 

With the latest release of android it now supports some Linux functionality. I got docker installed simply by following Docker's docs.

Any thoughts or uses for a mobile homelab? What would be useful to have mobile?

 

cross-posted from: https://lemmy.world/post/26434369

I want to compare the security of running my own:

  • Wireguard server
  • http proxy
  • socks5 proxy
  • Shadowsocks proxy

I currently port forward for wireguard, but would like some backups/alternatives, and censorship circumvention options. How risky or insecure are these protocols? Can I use them as normal VPNs into my homelab?

Any resources to research further?

Also: should I use my IP, or a domain? Which is better for censorship circumvention?

13
submitted 5 days ago* (last edited 5 days ago) by Dust0741@lemmy.world to c/selfhosted@lemmy.world
 

I want to compare the security of running my own:

  • Wireguard server
  • http proxy
  • socks5 proxy
  • Shadowsocks proxy

I currently port forward for wireguard, but would like some backups/alternatives, and censorship circumvention options. How risky or insecure are these protocols? Can I use them as normal VPNs into my homelab?

Any resources to research further?

Also: should I use my IP, or a domain? Which is better for censorship circumvention?

[–] Dust0741@lemmy.world 1 points 1 week ago (1 children)

I know it's not self hosting, but I went with a Hugo site hosted on Cloudflare pages. That way I don't have to port forward or worry about uptime or security.

 

https://github.com/wg-easy/wg-easy

Plus

https://github.com/qdm12/gluetun

The idea being; I can use a normal wireguard VPN from anywhere in the world to connect back to my homelab, all while being able to access stuff on my network, but also have my public IP address set by the gluetun container?

Anyone done this? Or have a docker conpose?

 

I have a collection of my docker composes and configs. I would like to have the ability to remotely (over Tailscale) deploy and manage remote servers.

This isn't necessarily for redundancy, but I would like an automated way to test and deployments.

I want to make a seperate homelab at my parents that I can remotly manage for them. I have multiple servers at home, so having all of the config in a git repo, and having my secondary computer use the test branch would be super nice.

My ideal scenario:

So say I want jellyfin. I make a compose and config on the test branch. It automatically applies to my test server. Once I confirm it works, it goes to the master branch. Then it gets applied to the production servers.

Can this be done? If so, can Forgejo actions do it?

 

I am wanting to automate some homelab things. Specifically deploying new and updating existing docker containers.

I would like to publish my entire docker compose stacks (minus env vars) onto a public Git repo, and then using something to select a specific compose from that, on a specific branch (so I can have a physical seperate server for testing) automatically deploy a container.

I thought of Jenkins, as it is quite flexable, and I am very willing to code it together, but are there any tools like this that I should look into instead? I've heard Ansible is not ideal for docker compose.