> We might not want to run our production database in Docker (perhaps we'll just use Amazon RDS for example), but we can spin up a clean MySQL database in no time as a Docker container for development - leaving our development machine clean and keeping everything we do controlled and repeatable.
Curious why you wouldn't want to run it in docker in production? Wouldn't running the same container in dev/prod be helpful?
One could argue it's more about the "thrills-per-minute" counts going up. I'm not saying I totally agree, but it is at least evident to me that movies from past decades spend a little more time between "thrills" than your average modern film.
I currently do this for the basics, and drop down to git at the shell for anything more complex than the one or two things GitHub's client does well. It's a decent trade off in my opinion.
My thinking was that expanding your underlying md RAID would be the same as replacing the initial disk ZFS sees with a bigger one, thus enabling easier expansion at the md level and presenting a "bigger disk" to the zfs vdev.
I haven't seen it done, it's just a theory, hence why I asked. I'm just not sure if zfs needs to see actual disks, or if it can work on top of any block device, like an md RAID.
> I assume they transfer it to local storage first before signing it so that a potentially malicious storage device can't pull a switcheroo.
In the article they mention it doesn't have local storage. It's too bad they didn't go into more detail about tamper proofing the USB portion of the ceremonies.
> This laptop has no battery, hard disk, or even a clock backup battery, and thus can’t store state once it’s unplugged.
I could be wrong and haven't explored the idea myself, but couldn't you accomplish this with something like ceph or scaleio and tmpfs/ramdisk for your block devices?
My experience is the same, 90% of unsolicited calls I get are from the same area code and prefix, only the last 4 digits are new.
I love how it makes it really easy for me to screen the calls however, as no-one I know has the same prefix and there are a couple area codes covering the local calling area.
Forgive me, it's Monday morning and I haven't yet had my coffee, but it sounds like you're describing a block-level copy between two drives, something which RAID0 is most definitely not.
Unless I'm misinterpreting, I think you were going for RAID1.
Agreed. They are a shining example of what I look for in a commercial company building an open source product. Self-hosted, community edition with no fundamental deficiencies, hackable, and a CEO with more 3rd party presence (he's always on here in the comments) than anyone could ever ask for.
I only wish it were written in something which compiles native, like C or Go. Not bad enough to switch to anything else however, and it's really just my own personal dislike for Rails/Ruby.
Love the Gitlab-CI integration too, and am excited to see how it grows/improves over time.
Also, can anyone speak to the current state of affairs with respect to ext4, xfs, and btrfs?
I'd love to hear about the tooling and code quality in these file systems from an informed (and recent) point of view. Has Redhat been putting out fires since the switch? Did it go unnoticed? Are there measurable performance and/or reliability gains?
Let's not forget they have a working Linux client. Maybe things have changed since I last looked, but they were one of the few supporting Linux (both cli and gui).