Yes it would. In my case though I know all of the users that should have remote access snd I’m more concerned about unauthorized access than ease of use.
If I wanted to host a website for the general public to use though, I’d buy a VPS and host it there. Then use SSH with private key authentication for remote management. This way, again, if someone hacks that server they can’t get access to my home lan.
Their setup sounds similar to mine. But no, only a single service is exposed to the internet: wireguard.
The idea is that you can have any number of servers running on your lan, etc… but in order to access them remotely you first need to VPN into your home network. This way the only thing you need to worry about security wise is wireguard. If there’s a security hole / vulnerability in one of the services you’re running on your network or in nginx, etc… attackers would still need to get past wireguard first before they could access your network.
But here is exactly what I’ve done:
Now I can just turn on my phone’s VPN whenever I need to access any one of the services that would normally only be accessible from home.
P.s. there’s additional steps I did to ensure that the masquerade of the VPN was disabled, that all VPN clients use my pihole, and that I can still get decent internet speeds while on the VPN. But that’s slightly beyond the original ask here.
A couple of options in my opinion, as I just did this myself:
You can use the CLI tool to “upload” them. You can even do this from the server itself. So upload times would be as fast as your network card can process or however fast your server is, whichever is slower. It does require that you create an API key for the user in question though.
Otherwise you can create an external library and link that to your account. Now Immich will still index this library but it won’t move or manage the actual files. I’m not sure though if it looks at those files for duplicates (i.e. if you try and upload the same photo from your phone to the server). This external library will also prevent deleting photos as well, FYI.
There might be other options that I’m not aware of, as I’ve only been using Immich for about a month now.
Edit: link to the CLI documentation: https://immich.app/docs/features/command-line-interface/
If the honeypot is set the request is simply discarded.
FYI: https://en.m.wikipedia.org/wiki/Honeypot_(computing)
But there should also be a separate endpoint to get an auth token. (I don’t remember it off the top of my head). Then your bot should store that somewhere and send it as the auth parameter in every request.
You can always try constructing the URL manually. I know this sucks, but it might be a workaround.
https://lemmy.ml/c/songaweek@lemmy.world
Long story short you just have to go to lemmy.ml and then add /c/ followed by the community name @ the instance it belongs to.
I’m also running Ubuntu as my main machine at home. (I have a Mac and do Android development for my day job).
But at home, I do a lot of website and backend dev.
docker buildxdocker compose up -dCloudflare? Namecheap?
Not sure exactly what features you’re after but the vast majority of them support what you mentioned above.
Not that I’m aware of. I already opened a request on the backend to have an API to provide a since= property. But ultimately found a workaround for my needs (not applicable here).
Assuming the fediverse becomes mainstream one thing I hope to actually see is that existing company forums start to join the fediverse.
Think if you no longer needed to login to EA’s website to post about bugs to the Sims. Or if Prusa’s 3d printer community forums could also be found right here… Or any other existing community help forum.
The problem though is, that in order to get there, Meta and others have to bring the users and essentially show the way first.
Last I checked AWS is a fairly expensive option to host a Lemmy instance. You can still do it, but there’s much cheaper options out there.
I know this doesn’t answer your question really but may explain why there isn’t a lot of details on using AWS as a host.
The project is open source so you can see what they are logging, if you can read the code.
But simply some things that are logged:
From what I can tell neither of these data points are federated so only the instance your logged into has that information.
** Don’t use this as an exhaustive list. These are just the two items you specifically asked about and what I’ve seen looking through the code so far. **
All of this looks fine. But incase anyone else has any ideas, here’s the results I found looking up the original error: https://github.com/docker/compose/issues/4189
https://raw.githubusercontent.com/LemmyNet/lemmy/main/docker/docker-compose.yml
...
services:
proxy:
...
lemmy:
# image: dessalines/lemmy:dev
# use this to build your local lemmy server image for development
# run docker compose up --build
build:
context: ../
dockerfile: docker/Dockerfile
# args:
# RUST_RELEASE_MODE: release
# this hostname is used in nginx reverse proxy and also for lemmy ui to connect to the backend, do not change
hostname: lemmy
Just copied this from the above URL. But just under lemmy: there’s a few comments and the reference to the build section. You’ll want to remove those lines. and just have:
lemmy:
image: dessalines/lemmy:0.17.3-linux-arm64
...
You’ll need to do the same thing for lemmy-ui, but it’s build section is already commented out but the default compose is using an incorrect tag for the Pi.
See below:
...
lemmy-ui:
image: dessalines/lemmy-ui:0.17.1
# use this to build your local lemmy ui image for development
# run docker compose up --build
# assuming lemmy-ui is cloned besides lemmy directory
# build:
# context: ../../lemmy-ui
# dockerfile: dev.dockerfile
...
so for it, you just want to change it to:
lemmy-ui:
image: dessalines/lemmy-ui:0.17.3-linux-arm64
...
Hmm. Well I literally just setup a Pi running a Lemmy instance last week. I can walk you through the steps that I took…
Ubuntu Server using https://www.raspberrypi.com/software/. Raspbian should also work with these steps, but I just happened to use Ubuntu Server. So feel free to skip this step.
Install Docker via these instructions: https://docs.docker.com/engine/install/ubuntu/. If you used these steps to install Docker prior, feel free to skip, but if you just did apt-get install... you may need to revisit that page.
created a lemmy folder somewhere on my machine. For the sake of argument, I’m going to assume /docker/lemmy for now.
3a) Create the volumes and pictrs folders and chown them as described in original documentation: https://join-lemmy.org/docs/en/administration/install_docker.html
Copy the docker-compose.yml file as described in the documentation as well as the lemmy.hjson. I placed the docker-compose in /docker and the lemmy.hjson in /docker/lemmy.
Edit the docker-compose.yml so that you use the latest pre-build images instead of building from source. To do that you’ll want to remove the lines that look like this:
build:
context: ../
dockerfile: docker/Dockerfile
and instead replace them with:
image: dessalines/lemmy:<tag>
but before we do that we need to determine the latest tags that are available to the Pi. You can look here: https://hub.docker.com/r/dessalines/lemmy/tags and here: https://hub.docker.com/r/dessalines/lemmy-ui/tags. For the Pi though the latest versions available are: 0.17.3-linux-arm64 for both the backend and the UI.
P.S. I did lookup the error you got and it seems to be related to Nginx. So if above steps don’t work, you may need to paste your nginx.conf file.
Are you able to post logs from both the lemmy container and the lemmy-ui container? That might shed some light as to which one is failing.
$ sudo docker logs lemmy
$ sudo docker logs lemmy-ui
You may need to run sudo docker container ls in order to find the actual container name for the two, as the default docker-compose doesn’t specify their names, so they’ll get randomly generated.
(I’m assuming the error you’re seeing from docker compose up -d is from lemmy-ui, and something else is failing or preventing the backend from starting, but that’s just a guess)
What phone do you have? I just upgraded last night and everything appears to be working like normal. But I did notice that you appear to have a smaller screen size than I do. First I’d try adjusting the display size and see if that helps. You can find that setting (on a pixel) under: Settings -> Display -> Display Size and Text.
You can also try adjusting the accessibility settings and increase or decrease the font size to see if that helps. Which you can find in the same menu above.
Lastly, you might try enabling developer settings and adjusting the smallest width:
Edit: none of these should be final solutions but to help troubleshoot what’s wrong. You can then use what you find with these three options to raise a ticket and hopefully the developers can then narrow down the actual root cause.