The ansible playbook just deploys docker containers. It does nginx proxy config, deploys the docker software, and then creates the compose file and deploys the containers. The reality is the ansible deploy and docker deploy both use docker. The ansible playbook just does more of everything all at once in an automated way.
Then what does it have a publicly accessible API for?
My process is similar, but i don't use the !ommunity@instance format. I just copy the url and search for it.
Search: "https://lemmy.world/c/selfhosted"
it will initially return Nothing found but after another second, it shows up and i can click it and then subscribe to get new posts and comments.
Of course, the real test will be when it comes time to update to the next Lemmy version…
it is easy enough. Simply run the playbook again. well, git pull the ansible playbook again and then run it. alternatively you can just use docker compose now on your lemmy server. I made some aliases on my lemmy instance based on what i use elsewhere. I think I got them from a linuxserver.io tutorial ages ago. you will need to adjust the container versions for this to be viable as the version is hardcoded and they only have a "latest" tag for arm.
alias dckill='docker kill $(docker ps -q)'
alias dclogs='docker-compose -f /srv/lemmy/lemmy.domain/docker-compose.yml logs -tf --tail="50" '
alias dcpull='docker-compose -f /srv/lemmy/lemmy.domain/docker-compose.yml pull'
I think the blackout is counter productive to continue. The idea was to try and convince reddit to change their minds, but as we can see now that is simply not going to happen. you can't convince someone who is unreasonable with logic. The way it has gone is that there has been a large influx of people trying things like kbin and lemmy, and the experience has not been smooth. lemmy.ml being immediately overloaded, and continuing to be difficult to federate with reliably is a problem, and not one just for that instance. It creates a sour view of the network (especially with other instances running into issues that seem to be scaling issues with the lemmy software). I think kbin has had some scaling issues that required using a large cdn to even try to cope with. The problem there is that if you look at the traffic of some of the largest federated reddit replacements, it is almost nothing in the grand scheme of things. The number of communities is very small, and those that exist have thread counts in the double digits at best. Most of that is due to the hyper isolation and fragmentation of instances due to federation issues at scale.
In the end I think every sub should call it a day on blackout. Go back to normal and make it clear that reddit hasn't won, you are just regrouping. Then give the software devs a bit more time to work before the 3rd party apps go offline for the final time. use the initial blackout as a scream test, and wait for reddit to disable themselves by revoking api access. Hopefully by then many of the larger issues with reddit like federated alternatives can be resolved, or at the very least minimized, so the transition away from reddit can take place quickly and easily.
Another distro doesn't magically fix difficulty for a custom setup. You can checkout other distros and see if maybe you like how they are laid out and how their package managers work, but the general config portion of deploying your apps is going to be the same regardless. Something to consider is how are you getting help for your setup? Is it some content creator you follow who generally does their videos/guides on ubuntu so that is how you figured everything out? Do you have friends or family who use it? If your source of knowledge and help is familiar with ubuntu, it is best to stick with it so you continue to have that resource. I can fumble around most distros, but if you want specific help, you are much better off asking me about specific issues inside an RPM based distro. I imagine others are similar in that they have generally applicable knowledge and a huge amount of specific distro knowledge since that is generally what they use.
I have a cheap food dehydrator i got on Amazon and it works fine. I mostly use it when I have multiple spools to dry, o if I have a particularly saturated spool. I will run for a few hours in the dehydrator and then move to spool dryer.
I had sain smart dryers, but i really didn't like how you set the temps. Instead of specify the temp, it had level 1,2, and 3 and depending on the number it meant a different set of filaments. I lost the manual at one point so I could never remember if ABS was 2 or 3.
I replaced that dryer with one from Tecbears.
https://www.tecbears.com/product-page/filament-dryer-box-white
It was a deal i found online at one point and I think it was $40 at that time ($20 off). I like it because you specify the temp you want it to heat up to. It has 2 heat elements so it heats the top and bottom of the spool and it has a readout for the current humidity inside the dryer. My only complaint with it is that it only goes to 70c. I had spools of ASA that say to dry them at 80c and I don't have anything that goes to that temp. I left it in the tecbears dryer for 24hrs at 70c and it seems like it printed better than it had in the past.
So the product looks really nice. Going away from the home project/Industrial looks and going more towards the home fixture look with the nice wood enclosure. My only concern with it is that their site gives very little technical details on the printers. What is the print volume? What board does it use? Does it come assembled or is it a kit? It would also be nice to see more of the interior so you can see if it is rail or rod based. It also doesn't seem to be a fully enclosed printer, so does it have a tophat option?
In the end, it is a kinda cool design but it doesn't seem like something I would go for at this point. I think there are tons of other option at that price point or lower that service the same functional purpose.
I'm using fedora for my main workstation at home. most of my servers are run on almalinux but I do have a few that are ubuntu and proxmox for virtualization. At work we only use and support RHEL.
I think this is one of the more sensible answers here. If your workstation is windows, then utilize WSL for ansible and deploy onto a ubuntu or debian host (I'm assuming it works fine on debian, I used ubuntu). You might run into some issues with ansible dependencies as the readme doesn't seem to cover everything from what i remember, but once ansible works and has the correct configs, deployment is super easy.