It might be worth looking more deeply into. From a cursory glance, it might be usable for my usecase, but many service have configuration examples for NGINX (or Apache if they’re old). I’ve never seen caddy examples. What has your experience been with adapting those examples to caddy?
Caddy is so simple you don’t really need configuration examples. The extra configuration many docker services have you configure in Nginx are already done by default with Caddy. Though I have seen Caddy config examples around sometimes.
If all you’re using it for is reverse proxying, you don’t need config examples for Nginx or Caddy, just understand how to configure them.
I agree with the dissent in this case. What kind of Alice in wonderland bullshit are we living in where when you say boneless, you actually mean “THERE MAY BE BONES OVER AN INCH LONG IN THEM!”??
Words have meaning. It really shows how much these fuckers are cutting corners. If anything it’s negligence for allowing a product such as this to reach the customer, get lodged in his throat, slice open his esophagus, get infected, and require two surgeries.
If the boneless wings had glass in them, would they be held negligent?
Here’s the bit of dissent from the article.
“Dissenting Justices argued that a jury should have been allowed to determine whether the restaurant and suppliers were negligent, and called Deters’ reasoning “utter jabberwocky.”
“When they read the word ‘boneless,’ they think that it means ‘without bones,’ as do all sensible people,” wrote Justice Michael P. Donnelly in dissent.”
I can understand tiny pieces of bone making it in there, but a 1 and 3/8ths inch bone. That’s nearly the length of the wing! It just seems like negligence on the meat processor (not necessarily on the restaurant)
I’d say the restaurant is in charge of final QC. They’re handling it while cooking. This doesn’t absolve the producer, but, they do have an obligation to serve safe food.
But I’m also pretty irritated by supposed wing joints passing off frozen Cisco foods wings as their own when all they do is heat them in a microwave and toss some sauce.
They toss the frozen wings into the fryer so that the breading stays crispy… The microwave ruins breading making it rubbery or mushy.
Equally as amazing as the processor missing a 1 inch bone is someone chewing so little that they didn’t notice the bone. You’re not a snake chew your food.
They toss the frozen wings into the fryer so that the breading stays crispy… The microwave ruins breading making it rubbery or mushy.
So… that second part is how I know they didn’t fry it. I know that’s how it’s supposed to be done. Or baring a fryer, baking- preferably in a convection oven.
Equally as amazing as the processor missing a 1 inch bone is someone chewing so little that they didn’t notice the bone. You’re not a snake chew your food.
Never judge a species by their eating habits!
In any case, it’s not really his job to check for bones. It’s not something he should be worried about; he may not even have been sober enough to notice or care.
Much like compressive or tensile forces, responsibility is perfectly capable of fully inhabiting every step of a series.
So if you put a linear stack of styrofoam blocks (negligible weight but some structural strength) and then put a 10 lb weight on top, every block in the stack experiences 10 lbs of force.
In the same way, I think every person along such a chain of custody can each, independently, be held fully responsible for a fuckup that makes its way down that line.
Some good answers in here already. It boils down to a couple points for me:
Back when I started selfhosting, it was either nginx or apache, and I found nginx better and easier to set up
All the nginx knowledge I learned years ago still works just the same as it did back then, so why potentially mess things up by switching if it all still works
Basically every project has an example nginx config for reference, that can’t be said about other proxies
It is easier to find support online for edge cases that might pop up with nginx due to the ubiquity of its use and years of history
Because I have it in use as my main webserver, sure I could put that behind haproxy too but why? I like to keep my server setup small and easy, without unnecessary duplications. Nginx can everything that haproxy can, and more.
Honestly, from your description, I’d go with Debian, likely with btrfs. Would be better if you had 3 slots so that you can swap a bad drive but, 2 will work.
If you want to get adventurous, you can see about a Fedora Atomic distro.
Previously, I’ve recommended Proxmox but, not sure that I still can at the moment, if they haven’t fixed their kernel funkiness. Right now, I’m back to libvirt.
Apache still is a pain in the ass. The only guide I found useful were from 20 years ago or so. All “modern” ones I found didn’t explain stuff, but were more like “copy paste this, now you’re done”. They never fit my usecase.
I honestly don’t know why people new to webhosting even bother with Apache when NGINX is around. It’s just so much easier.
If an HDD doesn’t work in every conceivable way out of the box it must be an RMA. These devices are too delicate to settle for anything less than flawless on arrival.
And also because for me it started from web hosting where Apache and Nginx dominate and later because of many easy to understand example configs from the net including many “docker letsencrypt” examples.
Get one of those masks that also cover your nose, it will make going under water 10000x easier, you just have to worry about closing your mouth. The way I learned was by hanging on one side of the pool and using the wall to give myself some insertia, and then figure out the movements to keep going. Doing underwater backflips can also be fun. I don’t to to public pools because they disgust me, but when I am in a pool I like jumping in and finding out the biggest splash I can make with friends. Stupid but fun stuff
kbin.life
Oldest