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:
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 can simply replace the -p 192.168.1.2:5314:5314 with -p 5314:5314.
No need to specify the IP unless your device has multiple (active) network interface and you want to specify which one to use.
You are then able to access by going to localhost:5314.
Additionally, you can skip the docker pull step, when the image is missing the second command will lead to it being pulled automatically.
You should however use it if you want to pull in a newer version of the image.
Mine definitely didn’t work until I defined the IP, and I got that idea from reports that others had posted online haha. Not sure what we’re doing wrong but there are dozens of us!
Good callout on the redundancy of the pull command, I didn’t even think/notice that!
Use Tailscale vpn if you want access from outside your home network. It’s super easy to set up, all you do is install Tailscale on the server and client, and login.
I’m also assuming that you are still running an Intel Mac, as wefwef for now doesn’t provide native ARM containers and you’ll have to build them yourself.
That’s the attitude, thanks for sharing your new knowledge.
Just running the docker run command should pull the image no matter what. So runing docker pull shouldn’t be mandatory.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
You can simply replace the -p 192.168.1.2:5314:5314 with -p 5314:5314.
No need to specify the IP unless your device has multiple (active) network interface and you want to specify which one to use.
You are then able to access by going to localhost:5314.
Additionally, you can skip the docker pull step, when the image is missing the second command will lead to it being pulled automatically.
You should however use it if you want to pull in a newer version of the image.
Mine definitely didn’t work until I defined the IP, and I got that idea from reports that others had posted online haha. Not sure what we’re doing wrong but there are dozens of us!
Good callout on the redundancy of the pull command, I didn’t even think/notice that!
Use Tailscale vpn if you want access from outside your home network. It’s super easy to set up, all you do is install Tailscale on the server and client, and login.
I’m also assuming that you are still running an Intel Mac, as wefwef for now doesn’t provide native ARM containers and you’ll have to build them yourself.
I don’t see them using
--platform=linux/amd64so I suspect you are correct, that they’re using an Intel Mac.Yes, apologies for not clarifying. It is an Intel Mac!
What happens when a new update is available? Do we need to run the docker again? (Noob here :( )
If you’re using the tag
latestthen you would need to re-pull the image and restart your docker container.That’s the attitude, thanks for sharing your new knowledge. Just running the docker run command should pull the image no matter what. So runing docker pull shouldn’t be mandatory.