• 0 Posts
  • 47 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle



  • At $dayjob I switched from Apache to nginx 15+ years ago. It’s Callback/Event based process model ran circles around Apache’s pre-fork model at the time. It was very carefully developed to be secure, and even early on it had a good track record. Being able to have nginx handle static content without tying up a backend worker process was huge, and let us scale our app pretty well for the investment of time. Since then, Apache implemented threaded + Event based process models, Caddy, traefik, and a bunch of others have entered the scene.

    TBH, I think the big thing nowadays is sane defaults, and better configuration, even automatically discovered configuration – traefik is my current favorite for discovering hosts in consul/Kubernetes/simple host definition files, but since traefik can’t directly serve files, I simply proxy from traefik to … nginx :)



  • I think it’s not widely front-and-center because it’s kinda fiddly, especially with folks with customized printers and there are caveats that can damage the machine or ruin the print if you are not careful. Sadly, I think that some of the more ‘closed’ slicer/printer systems could support it more reliably because the dimensions of the head + arm are much better known and the tool path can be planned much more precisely.



  • Keep in mind that if you slice multiple parts to be printed at a time, then a failure on one part means the whole batch is potentially compromised.

    I have the most experience with PrusaSlicer, and have used the multiple part one at a time option to print multiple parts at once. You have to tell it the dimensions of your extruded head, so it doesn’t crash the part , and if you have a bed slinger, you have to be careful of your x axis bar (ie, order it so it starts at the front if the bed and works it way to the back)

    With mainsail and klipper, you can cancel one failed part mid print and keep going on the rest of the parts.