this post was submitted on 02 Jul 2023
65 points (92.2% liked)

Selfhosted

40018 readers
769 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
65
How I self hosted wefwef on macOS with Docker (lemmy.world)
submitted 1 year ago by kobra@lemmy.world to c/selfhosted@lemmy.world
30 comments fedilink hide all child comments
 

I posted this as a comment in the wefwef community but thought it might also be relevant here. If anyone is interested in self hosting wefwef this is how I did it on macOS:

Start by installing Docker desktop

Open Terminal and type in:

docker pull ghcr.io/aeharding/wefwef:latest

Then, you need to use a Docker run command like below to get things started. In this example, I put my local IP in as "192.168.1.2" but you'll need to adjust that value to whatever your machine's IP is.

docker run --rm -d -p 192.168.1.2:5314:5314 -e "CUSTOM_LEMMY_SERVERS=lemmy.world,sh.itjust.works,lemmy.ml" ghcr.io/aeharding/wefwef:latest

At that point, I went to my iPhone, opened Safari and went to 192.168.1.2:5314 and boom, there's wefwef. Install this as PWA and name it (local) or something to differentiate it from the normal wefwef and you're good to go.

Disclaimer: I’m brand new to all of this so I’m sure this isn’t the best way. But it got me started, so I wanted to share.

you are viewing a single comment's thread
view the rest of the comments
[–] PlutoniumAcid@lemmy.world 8 points 1 year ago (1 children)

Why is that pointless? Does it not take load off the server?

Also of course it educates OP on this cool tech, but that's not what I am asking.

[–] mattes@lemmy.kussi.me 3 points 1 year ago (1 children)

Not really. It’s a PWA so as long as you „install it“, it should talk to wefwef servers at all.

[–] MiddleKnight@discuss.tchncs.de 2 points 1 year ago (2 children)

I am pretty sure I read that all traffic is proxied through wefwef servers. It has to be this way due to lemmys (lack of) CORS settings. I think there is some work towards changing this.

[–] CriticalMiss@lemmy.world 3 points 1 year ago

Well if you host your own instance, your traffic originates from a different source.

[–] iso@lemmy.com.tr 3 points 1 year ago

If the traffic is proxied through wefwef then its not pointless. IDK didn’t checked.