317 karma · joined September 4, 2014
edit: thanks M$ for messing up another beloved solution.
They have minimal tooling, poor change management, poor logging, inability to address broken state and no support what so ever for a service you paid for. I won't go back to their hosted ES.
Edit: spelling
Keys issues i've seen in our Enterprise install... * Upgrades can go bad, very quickly and very silently. * Build images are out-dated, missing security patches, bloated, and not easily provisioned with custom features to integrate our tools with theirs. * no tooling for docker builds/deployments * long start up time on the build images. * Enterprise documentation (though it's been improved a lot recently)
Best of luck to #travisAlums, I hope you get picked up quickly.
you can version pin your apt packages if you need to, i personally prefer the minor patches so i get my security updates. my build tool will catch if there's a bug affecting my software.
> Is this any different from what you do in a shell script on a server?
yes, because I can take that built image and deploy it to any host and all my developers get to all use the same one in their development. but hey, if you like building with shell, you could try out packer and run that shell script to create an image; which can safely be used on any host that supports docker or kub?
> I don't see how a docker image definition makes any of this easy. There's not even a flag to disallow network access during "docker build".
Easier depends on your goals and perspectives. For me, it's easier to write a docker file that installs what I need to run a service. Where bash doesn't have that, it's just a script that needs an environment to run. where do you run bash? is it locally on your OS with your packages with your settings and your needs? what happens when I run that bash script in a different OS? Who's going to debug that? Are you going to track your changes made in version control? how do you update the other servers/users who use your script? I got other fun things to do than worry about that.
this is pure fud; spinning a reported security vulnerability as if it was his competitor trying to hack the election?! that's begging for a lawsuit in the least, too bad he's the controlling attorney general to boot.
this from the same guy who just recently said he didn't need any help with election security in Georgia... fire him.
I'm all for companies growing and learning from mistakes, the credit companies have a higher standard to live up to and should have a very steep cliff to jump off if they mess up.
2. trust no one, not even yourself.
3. hard work, is money in the bank.
4. with two paths in the road... take the scarier one.
5. pay off your debts faster than expected.
6. give more than you get.
7. listen more than you speak.
8. always be prepared, to find another job.
9. love unconditionally.
10. try not to think in absolute terms.
11. everyone has a story
edit: format
how about we barter, we'll give a smaller range (a fixed rate really isn't a good reality) and then the ISP's have to disband their lobbying efforts for ten years. Also they need to undo each state and local law they had put in place to prevent city and states from creating their own local ISP service. Oh, and Pai has to quit and be banned from working at any ISP for at least two decades.
i'll be here waiting with my full support to these terms.
I think there's opportunity for the scooter companies can mitigate the abandonment or carelessness of their products by using some thoughtful software. If someone leaves a scooter tipped over, they get banned for a day. Do it again, they get banned for a month. etc... Maybe have a clearing house to monitor cross service users are bad actors?
0. Compiled Security Alert RSS Feeds
1. Hacker News
2. Tech Dirt
3. AWS - What's new
4. Muck Rock
5. Pen Test Blog
6. dev.to
7. cso online
8. One random choice from my local news sites.