It was just how the settlement was worded; this team is prevented from distributing “anything that circumvent’s Nintendo’s blah blah,” and Citra was developed by the same team. So, it got taken down all the same :(
It was just how the settlement was worded; this team is prevented from distributing “anything that circumvent’s Nintendo’s blah blah,” and Citra was developed by the same team. So, it got taken down all the same :(
Great work, thanks!
Anything on Citra? PineappleEA made it easy enough to also download binaries for Yuzu, but I’ve got nothing but a flatpak for Citra.
A central place for binaries of both emulators would be great.
Both flatpaks are still available, by the way:
https://flathub.org/apps/org.yuzu_emu.yuzu
https://flathub.org/apps/org.citra_emu.citra
They can be bundled and exported after downloading, although it will only be for the architecture of your machine.
Neither of those are issues:
Unfortunately, there is not a lot of information to go off of here. I was able to upgrade to 0.18.4 with no hitches, and I haven’t seen similar reports of this.
Are you using any custom configs? Do the logs for just the Lemmy service show you anything of note?
docker compose -p lemmy-easy-deploy logs lemmy
In the past, Lemmy itself has had some strange edge cases causing crashes, such as an improper audit log value causing the entire audit log to fail. It’s possible this is a similar case, in which case you may need to file a bug on Lemmy’s tracker.
You are welcome to file an issue with some more information and logs, but if this is an issue caused by a bug in Lemmy, unfortunately I won’t be able to fix it.
If you’re still having issues, feel free to give me some more info on my tracker and I can take a look:
You should be able to use the SMTP options in config.env to use Mailgun!
A fully 3D remake comes out in just a few months! I can’t wait!
Yes, you will want to copy the entirety of the Lemmy-Easy-Deploy
folder recursively, including the live
folder.
However, all important data is also stored in Docker volumes on the system. There isn’t a great way to migrate Docker volumes between systems, but there are a few options. One I have not personally used, but seems to look good, is vackup
:
https://github.com/BretFisher/docker-vackup
You’ll want to run docker volume ls
on your current system, and make sure that when you migrate them to the new system, all the volume names are exactly the same. Then, if you run deploy.sh -f
, it should pick everything up and deploy.
Do note: if Docker Compose itself does not create the volume with the right tags, it will still work, but it will print some warnings to the console. Here is an issue discussing it and some potential hacks you can use to add the right tags:
https://github.com/docker/compose/issues/10087
Finally, if you need to re-create a volume on the new system with tags like the above issue mentions, you can try migrating data over between named volumes on the same system using this helpful oneliner (don’t forget to change the volume names in all the places in this command):
https://www.commands.dev/workflows/rename_docker_volume
In short, it’s a bit hacky, but it can be done.
Good luck!
Unfortunately, Lemmy Easy Deploy isn’t well suited for running behind a reverse proxy. It is a complete “do everything for me,” and I don’t have a good way to support people running a webserver already. I’ve pushed an update a few minutes ago, so you can try playing with the ports and maybe turning off Caddy’s TLS (so that certificates are managed by your webserver instead of the one in LED), but I’m sorry to say you’re on your own in that case :(
Lemmy can basically run on a potato. Any VPS will do, but the main metric you’ll want to keep track of is disk space. Any $5/month instance will be fine.
I am a moderate-to-heavy user of Lemmy, and I go through about 700MB of new data per day. If you federate with less communities than me, this may be less for you. At my current rate of storage, I can go for about a month and a half before I have to worry about storage space.
After that, I’m thinking about clearing my thumbnail cache, and seeing if Lemmy has some way to prune old data. I haven’t been using Lemmy long enough to know what to do to clean things up, but if I figure out something clever in a month or two, I’ll share what I learn.
EDIT: Turns out ~90% of my Lemmy data is just for debugging and not needed:
https://github.com/LemmyNet/lemmy/issues/3103#issuecomment-1631643416
Bro…