You can go a lot higher than 1000 without optimizing for UPS, they’ve made a lot of performance improvements over the years. Highly hardware dependent, of course
You can go a lot higher than 1000 without optimizing for UPS, they’ve made a lot of performance improvements over the years. Highly hardware dependent, of course
Which is why it’s a bottom tier private tracker
Edit: it’s actually not that bad but the rars are annoying and they should stop.
Private trackers tend to be more curated and better organized. Decent filenames, consistent organization and quality, correct metadata, no missing episodes or tracks, no RAR files, etc
I definitely see your point, but the difference is that it’s one thing to learn. Once you know docker, you can deploy and manage anything.
Cons of containers are slightly worse disk and memory consumption.
Pros:
Stick with the containers
Oh nice! I’m stoked about the background sidecar operations, that will speed things up considerably
but there is a reason i just explained it to you
Ok but is there room for the idea that your intuitions are incorrect? Plenty of things in the world are counter-intuitive. ‘docker-compose up -d’ works the same whether it’s one container or fifty.
Computer resources are measured in bits and clock cycles, not the number of containers and volumes. It’s entirely possible (even likely) that an all-in-one container will be more resource-heavy than the same services split across multiple containers. Logging from an all-in-one will be a jumbled mess, troubleshooting issues or making changes will be annoying, it’s worse in every way except the length of output from ‘docker ps’
I can see why editing config files is annoying, but why exactly are two services and volumes in a docker-compose file any more difficult to manage than one?
I disagree with pretty much all of this, you are trading maintainability and security for easy setup. Providing a docker-compose file accomplishes the same thing without the sacrifice
If you need honest-to-god office, then yeah you’ll need a windows installation. Either a VM or a second drive is best.
You can use windows indefinitely without activating, you’ll just have the watermark and default desktop background.
Seems fine, but you’re sorta hitting two fields at once. Application development (coding) is a different skill set from devops/deployment (docker). I’d stay pretty surface level on docker and the CLI for now and focus on building your app. You’ll know when you need to go off and learn those things.
Your best option by far is to overwrite windows completely. For most software development Linux is way better anyway.
I haven’t done this recently enough to guide you on the details, but step zero is to decide whether you are certain you want to dual boot or not. It adds a lot of complexity and brittleness that is best avoided if at all possible.
Miniflux has served me very well for years, combined with a few different apps. Reeder on iOS, I can’t remember what I used on android but there were plenty of options
Software & Services:
Destinations:
I’ve been meaning to set up a drive rotation for the local backup so I always have one offline in case of ransomware, but I haven’t gotten to it.
Edit: For the backup set I back up pretty much everything. I’m not paying per gig, though.
Im so excited to finally get icc color calibration
Oh cool, this is exactly what I was looking for! Thanks :)
Yes, “It’s us or the porn”, yes this will certainly go well for the republicans, no notes
Got a 3 year old kid with another on the way. I just need it to be reliable so the kid can watch Sesame Street and the lights keep working.