wefwef

4217 readers

1 users here now

wefwef is now Voyager! Subscribe to [email protected].

founded 2 years ago

MODERATORS

aeharding

How to self-host wefwef? (self.wefwef)

submitted 1 year ago by PlutoniumAcid to c/wefwef

13 comments fedilink hide all child comments

I believe that self-hosting will take some of the load off of the wefwef server. That will be a win-win for everyone. At the same time, I understand that wefwef is still so very new that it might not be mature enough to let loose on other people's servers.

I am looking for instructions on how to self-host wefwef, ideally as a docker container, ideally using a ready-to-use docker-compose.yml file.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (3 children)

pull image docker pull ghcr.io/aeharding/wefwef:latest

start container: docker run --rm -it -p 5314:5314 wefwef

Source : https://github.com/aeharding/wefwef#prebuilt

[–] [email protected] 2 points 1 year ago (1 children)

When I self host in my private network, wefwef should work from abroad as it‘s loaded on my phone - but does it pull new posts then?

[–] [email protected] 1 points 1 year ago

As long as your server is running and connected to the internet it should update new

[–] kobra 1 points 1 year ago* (last edited 1 year ago)

To clarify a couple of things, and hopefully help anyone else doing this on macOS:

Start by installing Docker desktop

Open Terminal and type in:

docker pull ghcr.io/aeharding/wefwef:latest

Then, you want to use a Docker run command like this 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 and you're good to go.

[–] CriticalMiss 1 points 1 year ago

Instead of doing 5314:5314 do 127.0.0.1:5314:5314. The setting provided in your post bypasses your firewall settings (assuming you're on Ubuntu Server, that's ufw) and set up a nginx reverse proxy with certbot.