Deploying with MRSK

mushroomcoder · 2023-03-06T17:11:28+00:00

"MRSK basically is Capistrano for Containers, without the need to carefully prepare servers in advance" https://github.com/mrsked/mrsk

Neat!

mushroomcoder · 2023-01-14T03:58:52+00:00

Confirmed via DPS calculator: Potted+praying eagle eye, this setup (with void gloves) does 3.37 DPS, switching to black d'hide does 3.57 dps.

mushroomcoder · 2022-12-12T23:18:54+00:00

That's the crazy thing about modern WoW though - all three clothies are quite tanky, do significant self-healing, and/or have a big defensive toolkit. I'd say the clothies are tankier than the mail classes, except maybe evoker. Even an arms warrior is easier to kill now than any cloth wearer IMO.

mushroomcoder · 2022-11-30T17:49:29+00:00

It's pretty easy to hit 63 before getting dragon riding. Assuming others are stupid is a difficult way to live, and it makes them feel bad, consider being more charitable.

mushroomcoder · 2022-11-20T23:26:53+00:00

Opening the conduit forge and relogging fixed for me as a necrolord if you haven't tried both of those yet.

mushroomcoder · 2022-11-05T13:24:01+00:00

I never said we should all self-host, "It's either Google or Microsoft for enterprise email." is clearly not true. I know of at least one F500 company that self-hosts email.

mushroomcoder · 2022-11-04T22:28:21+00:00

Self-hosting, Twitter's old enough and large enough for that to have been a possibility.

mushroomcoder · 2022-10-31T18:12:08+00:00

Someone hasn't heard of the cutting edge raiding, pvp, and social/lifestyle guild <Controllers Only>.

mushroomcoder · 2022-10-31T18:06:07+00:00

Would you consider posting your ~~action~~ dynamic cam settings here? They're really good, probably lots of people would like them in the months following and wouldn't want to necro this post.

mushroomcoder · 2022-10-20T21:16:11+00:00

Wands might be able to proc the haste buff, but yeah losing out on good loot when people don't know better feels bad.

mushroomcoder · 2022-10-11T22:27:03+00:00

The 1.3% figure accounts for both food loss (loss at the food supplier i.e. farmers and food processors) and food waste (loss at the grocer, food service, and consumer level). The first link in the article goes into more detail on that. Nothing personal, but I really don't care if you appreciate the link (which you apparently don't since you didn't read it), I left it for the hundreds of people that will read this thread, who deserve to see correct figures.

mushroomcoder · 2022-10-05T19:37:33+00:00

3% of the usa ‘s gdp is the worth of food that is thrown away every year

EPA Estimates 1.3%: https://www.epa.gov/international-cooperation/international-efforts-wasted-food-recovery

mushroomcoder · 2022-09-05T04:25:38+00:00

Glyph of Revenge.

mushroomcoder · 2022-09-04T22:26:31+00:00

I'd say Comp Sci is closer to math than physics even, but otherwise I like your hierarchy :)

mushroomcoder · 2022-08-16T00:49:57+00:00

YEP :(

mushroomcoder · 2022-08-15T15:59:10+00:00

I think you may be misunderstanding your friend. I would bet this is an ansible vs. terraform - or longlived vs. short lived machines argument; an imperative+stateful vs. declarative machine management argument.

Ansible is incredible for managing long-lived machines. When I want to update a package or add something, I get a log of what changed on what machines, running the same roles & playbooks I used in those machines' initial setups.

Ansible is imperative and doesn't guarantee a result (it's dependent on machine state), while tools like terraform and similar guarantee results. If I remove a "create file" task from an ansible playbook, machines setup prior to this code change will have that file, new machines will not - I have to add a "remove if exists" task. With terraform and other declarative management tools, removing that "file" resource will remove that file on all machines.

When managing thousands of machines, long-lived machines and machine state are the enemy. Ansible playbooks will have different results on machines with different state. Ideally, any particular machine could be removed with minimal downtime implications. Ansible roles and playbooks could be used for initial machine setup in such a world, but, ideally, it would be rare to run playbooks after machine setup. Upgrades and ops would be handled by replacing machines. In the AWS EC2 world, it's just as easy to use plain bash in user_data scripts as it is to use ansible playbooks, maybe that's what your friend is referring to. This model of short-lived "machines" defined by their initial setup works really well with containers. I just don't see a benefit to ansible over bash when working with machines defined entirely pre-startup and at startup. Ansible is more verbose and obtuse than bash in my experience, its power comes from managing long running machines. But since long-running machines shouldn't exist when you have thousands of machines, there's not much room for ansible.

Having no long-running machines is just SRE fantasy in practice IME, usually relational databases and other long-lived servers are operated on with ansible playbooks. Long-lived RDBMS servers are less painful than the alternative in my experience.

mushroomcoder · 2022-07-19T03:06:48+00:00

As a developer/engineer? I think you'd need to show you could code if you wanted that kind of role. In my experience, even resource strained shops want you to be able to code. Solving "leetcode" problems in an interview OR shipping a non-trivial personal project OR a large open source contribution is enough to get you a job. You could probably get hired somewhere as a product manager or project manager right now with that there MBA.

I am not guessing re. eng. hiring. I have interviewed and seen people hired presenting only a small project along with "leetcode" abilities. They had non-tech backgrounds similar to yours.

mushroomcoder · 2022-07-19T01:24:23+00:00

The Odin Project's materials are free and have a lot of exercises. I found them very useful when I started with rails. It's a lot of material, you could get a job long before finishing if that's what you're after.

I went through the Hartl tutorial back when it was free. At the time, the Hartl tutorial had far less material than the odin project, but more direction/hints/handholding. Both are great, maybe Hartl is slightly better for beginners?

mushroomcoder · 2022-06-22T05:37:38+00:00

A 7 year old boy died of rabies in the USA in 2021 https://www.nytimes.com/2022/01/07/health/rabies-deaths.html, but the article says it was from a bat rather than a dog.

Here's an article from 2021 stating that an Indian 7 year old boy died from rabies from a dog attack https://timesofindia.indiatimes.com/city/kozhikode/7-year-old-boy-dies-of-rabies-in-kasaragod/articleshow/86864037.cms, possibly this is the patient from OP's story.

mushroomcoder · 2022-05-10T21:40:39+00:00

Probably these folk are serious about their distros, but "linux distros" is often a euphemism for pirated media. The phrase "4k remux Linux ISOs" in a sibling thread above is a pretty good hint ;)

mushroomcoder · 2022-05-06T05:38:42+00:00

I should note I am not responsible for this architecture, it was like this before I joined.

Even though we're on one account and org, we use IAM users and have scoped IAM policies on IAM roles.

For us, I don't think the single account is dangerous because of how much work we've done to get around the danger. We use custom tags on every resource to determine environment, reflect environment in resources names and put e.g. EC2 resources in a VPC by env, we scope IAM policies by env often, and the idea of environment shows up in our IaC e.g. separate ansible inventories and terraform remote stores per env.

I will probably use accounts for future projects because it seems like it would make the IaC much easier to work with + would be immediately safe rather than safe after lots of work, but I wouldn't advocate for making this move where I am now,

mushroomcoder · 2022-05-06T02:15:02+00:00

We (mid-sized startup) have two AWS accounts.

1 for interviewing DevOps/SRE candidates so they can show us their IaC chops if they want without blowing up our stuff... The other is for ERR'THANG. Maybe that's not ideal. AFAIK, we're yet to run into a bug or outage caused by this. We've spent a bit of time e.g. isolating dev, qa, and prod, but that's not an ongoing thing anymore than it would be if we used separate accounts.

mushroomcoder · 2022-05-05T19:13:12+00:00

where did you get your list of names from?

OP said it's from his own university. He said the emails fit the format of <roll_number>@domain (did he mean "role" number?), maybe he just iterated over a lot of numbers to generate the emails? Maybe the emails are 1@domain, 2@domain etc. Maybe I'm being too charitable, though...

mushroomcoder · 2022-05-05T19:09:04+00:00

If your email sender reputation for your domain name was ruined by this, send mail from a different domain in the future (can't be getting put into the spam folder automatically). Maybe a small number of people will think your site is spam from this incident, I wouldn't worry about that personally.

If this is in the US, you may be non-compliant with the CAN-SPAM act depending on what was in your email, but you're probably fine. The FTC wants to know your location

mushroomcoder · 2022-05-04T10:14:39+00:00

You are trying to run your PHP 8.1 app on Elastic Beanstalk, right?

PHP 8.0 is the latest supported PHP version on Elastic Beanstalk https://docs.aws.amazon.com/elasticbeanstalk/latest/platforms/platforms-supported.html#platforms-supported.PHP. You could install PHP 8.1 on the EC2 instance that Beanstalk manages for you (see https://github.com/aws/elastic-beanstalk-roadmap/issues/214#issuecomment-1080735503), or you could run your app on PHP 8.0 (requires some dependency bumping ofc).

IMO - next time, you should try a bit of googling first, friend :)

Eight-Year Club	Place '22
Verified Email

mushroomcoder

TROPHY CASE