cereal7802

fucking no!!!

Yeah, I would say most people looking to build a voron should go trident. The v0 is tiny and brings about some finnickyness as a result, and the v2.4 has all sorts of belts and is generally more complicated.

You have 3 very different things listed there.

The K1: Creality printer with many issues. Yeah it is fast corexy, but they keep having to pull it from sale and people still have it falling apart or trying to rip the hotend out of itself. Personally, I would avoid it.

Bambu Labs: 3d printer company. They have 2 different printers to choose from. The X1 carbon being the flagship, fully enclosed corexy printer. I have one and while I like it, I don’t like the reliance on cloud and how locked into Bambu labs parts you are with it. As an example, a company designed and manufactured a small batch of hotend for the X1 that would boast higher flow rate and used a more normal round ceramic heater. When they asked Bambu if they could provide information on how to pid tune the new heater, bambu said “you don’t. We do that at the factory”. They have even stated they won’t be opening that ability up so you will almost certainly never see an aftermarket heater for the bambu printers. The other option is the P1P. It is the same basic printer as the X1, but it is not enclosed and some of the features are not present such as the lidar and chamber carbon filter. If going bambu, I would probably suggest the P1P as is it cheaper (They just reduced the price $100) and works really well.

Prusa XL: Larger format Prusa printer. It also has the option for multiple print heads so you can use different filaments on a print (I think it will allow for different nozzle sizes too) without needing them to be the same temp, and without the need for purging, saving time and materials. Unless you need the additional material support, I personally consider other options. The Prusa MK4 makes more sense for most people and even then, with Prusa having higher pricing for their printers, you might find something for roughly the same price that is larger and has more serviceable parts (with the MK4 you are pretty much locked into Prusa for replacement parts, and not real upgrades or after market exist). The downside to similarly priced alternatives being much assembly is required and you may not feel comfortable doing that.

In the end you have to consider what you are looking for, and compare the features of the available options. Of the things you listed I would feel perfectly happy with either the Bambu options, or the Prusa options, but for the home user I think the Bambu options work out better. For me, I went Voron 2.4. I bought my Bambu x1 carbon so i could print ABS parts more easily. Once the 2.4 is built I suspect the Bambu will spend most of its time in the closet until I find a multi color print I want to do.

With that said, waiting doesn’t make sense. Most of what you are looking at are recently released and not really do for a revision. You also have to consider things in the 3d printing world happen all the time. There isn’t a cycle of new stuff like with computer hardware. If you are in the market for something new, look at what is available and see if anything fits your needs. As long as you are making a decision based on what is the latest at the time of purchase, you are probably not going to miss anything.

As the costs to run/win go up, the expected return is greater.

I ran into some dependency issues(needed to install ansible-collection-community-docker on my fedora workstation), but after that it ran fine and installed everything first run. I made some adjustments to the inventory config afterwards, but aside from that it just worked.

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.

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.

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’

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’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.