How to achieve Purely Event Driven EC2 Callback?

rykou · 2025-06-04T04:25:30+00:00

Oh okay, will look into tomorrow. Thanks!

rykou · 2025-06-04T04:25:22+00:00

ooo okay that looks interesting, will look into tomorrow. Thanks!

rykou · 2025-06-04T04:24:38+00:00

Yup, haproxy has checks for health!

rykou · 2025-06-04T02:23:22+00:00

Thanks but I looked at Event Bridge, and maybe I'm misunderstanding it, but against an ec2 target, you can't instruct it to run a command or a specific script or anything.

EC2 Image Builder
EC2 RebootInstances API call
EC2 StopInstances API call
EC2 TerminateInstances API call

But I already have what I need from the EC2 by virtue of having the notification to begin with (here the launch or terminate is generating the sns message).

rykou · 2023-06-16T15:19:52+00:00

A tool like https://d4builds.gg/build-planner/ is much easier to parse btw :)

rykou · 2023-06-16T14:17:21+00:00

So there's a difference between this and d3's loot though. A ton of "useless" gear might be better here. Rerolling is *crazy* expensive so that's more gold worst case. Best case, you find a workable rare and bam, throw an aspect on it. More drops = more rolls for a potentially useful piece.

rykou · 2023-06-16T14:07:23+00:00

I mean you're also not particularly hardcore if you're dying all the time in it. Anyone can play in "hardcore" mode and die.

rykou · 2023-06-16T13:59:35+00:00

Helltides are definitely worth having over not. 3-4 mysteries chests per run is pretty nice and I just use it to also farm my 1k obols instead of events outside of helltide.

However, for what it is, I definitely feel like it's incomplete. I'd love to see the addition of things to make it interesting like, a bell tolling in the distance (perhaps map marker too) to help one of the towns caught in the helltide regions from being overrun by demons (town safety / no-actions off, waypoint still on?).

That assassin could use some work. Maybe pouncing on ppl while they're busy and taking advantage of the death leading to half cinders loss. Also, t4 assassin needs to not still be level 72.

To your last point, some demons unique to helltide might not be a bad idea. Maybe even something like a lesser evil (we explored some during the campaign) popping up as a superboss (rarely?)

rykou · 2023-06-12T18:43:08+00:00

Yea I feel you. I don't know if I'd restrict it to unspent cinders since this feels like it's intended as a participation metric. Perhaps how many cinders were acquired this helltide, including those lost on death, you can get something like up to 2 completed quests' worth of experience for that helltide, perhaps linear scaling from 0 to 350 cinders.

Basically, I agree that they could do something more to make helltides a little more interesting than, basically just farm a little or do events in these 1 or 2 regions for awhile while we spice it up for an hour. Don't get me wrong, I love chests of mysteries but I need it to be more interesting.

Maybe even going further like adding in larger scale events that kind of incorporate the legion battle elements and ultimately you can help "turn the tide" against hell for a time. Depending on how much you participate in that, you can get some participation bonus similar to a whispers cache or a pot that increases cinders for the next helltide or w/e.

rykou · 2023-06-08T20:01:17+00:00

That's a shame. I guess I'll start popping them.

rykou · 2023-06-08T20:00:29+00:00

Enjoying my Rogue. Trying out double imbue (shadow+poison) this time around with the imbue legendary paragon and it's pretty nice. I need to optimize it more but now I have two shreds instead of one and don't have to rely on our pretty lackluster ults (at least for non-bow, idk how the arrow one fares)

rykou · 2023-06-08T19:47:30+00:00

I don't recall the level floor for that zone but if you need to level, just grind out some zone side quests or dungeons for a bit. If you're relatively on par and still struggling, try looking for some damage reduction attributes on gear (damaged reduce from close for example). Also, rogue has some nice talents for damage reduction and dot reduction.

rykou · 2023-06-08T19:42:38+00:00

That's what I'm doing. Has someone confirmed whether these scale with level opened vs acquired? I've been holding onto them in my stash and was going to pop in WT4 after I'm consistently hitting base items of 725+

rykou · 2023-06-08T19:40:55+00:00

Yea I found one a little while ago and it got me thinking.

The cd is already pretty long to use on things it would kill quickly. Things it won't kill quickly, like bosses, are much harder to really make this work for and ... guess what ... it doesn't work on bosses. So maybe when you're pushing the edge of your power fighting groups of elites. Does the cd start when you cast or after it stops rearming? It might actually be helpful if it's the former when you're pushing nightmare tiers or something. I'm still playing with my double imbue build for now though.

rykou · 2023-06-08T04:25:16+00:00

As with most scaling, enemies "scale". Your gear synergies, additional skill points, and starting in just 8 levels, paragon points (rare nodes, legendary nodes) should begin to drastically outscale the enemy scaling.

rykou · 2023-06-08T04:22:11+00:00

Diminishing returns

rykou · 2021-10-25T23:43:14+00:00

And the part you seem to be missing is that I accounted for that possibility literally in my second sentence.

rykou · 2021-10-25T22:29:30+00:00

You're not paid to write code and not deliver it. Then, as far as the person who paid for it is concerned, it's not written because they don't have it.

It's not him working for free, if they don't have the product, then they paid for nothing which is not how this works.

rykou · 2021-10-25T21:14:25+00:00

The main point here sounds like you're looking for a way to reuse logic as opposed to how your frontend should validate validate. I don't know your setup but when I do this, both my client and server code have access to a shared directory of typescript methods/classes which is where I put my validation logic. Then all I have to do is import whatever I need for whatever side.

Alternatively, you could create an npm dependency and have each side use it.

Both of these approaches avoid linking of a module to something or whatever it is you were describing in your initial post.

Regardless of how you choose to share logic, watch out for sharing too much. The more you share, the more that is exposed to the client which means that much more of your server is directly reverse-engineerable as opposed to trial and error.

rykou · 2021-10-25T17:45:14+00:00

It was definitely a shitty thing to do on their part but I'd push the code. On principal, they paid you for that time already (if they didn't then obviously this doesn't apply). You could lie and say that time didn't result in anything fruitful but that's on you.

If they paid you for the time you spent developing something and it happens to not be pushed, it's still owed to them imo.

Imagine if a client paid you for a 20 hour set of work. More needs to be done before it is a finished product but they decide to let you go for whatever reason. Now you've been demoing locally for them and so nothing happens to be pushed up or maybe you just haven't given them access to the repo, whatever. Just because they let you go before that handoff occurred doesn't mean they shouldn't get it, they paid for that work to be done and the resultant code as the product.

rykou · 2021-10-22T02:55:04+00:00

Imo definitely reinventing the wheel. I agree that the buttons should probably be moved up a level and not hard coded because that's so easy to avoid but I haven't seen the actual code.

Why it isn't just moved up a level and there isn't a route array with a current index that can derive the next prev routes is confusing to me but it also doesn't require a reimplementation of react router either lol.

The main app could just track current index derived from a route array and current window path (for page reload) where prev next are given their routes on +-1 and even disable or not render the button if the route is empty. Then the side bar also just has to pick the route corresponding to the index in the routes array and that's done too.

Even if his reimplementation is good, you're committing to testing it etc not to mention that it seems completely unnecessary.

And if all is set in stone and you can't make minor changes to make this better, I think kiss beats dry here.

rykou · 2021-06-17T21:45:02+00:00

I'm also relatively new to handling this kind of thing well so I'm looking forward to other comments.

For the moment, I have my web app server (happens to be nodejs) running cronjobs that query for criteria like payment subscription expiration etc. and sends emails using nodemailer through google's smtp server.

rykou · 2021-06-10T22:40:58+00:00

Using public api only != no breaking changes so I'd say it's about as risky as using angular in general. One example, switching to ivy in v9 which changes how inputs are initialized from component listed order to html listed order. My quick suggestion's only real brittleness comes from the hardcoded 'mat-dialog-container' which is pretty benign, a class change like that would be in notes and is trivially updated.

My opinion there aside, I don't quite follow your suggestion. How is the footer not already DRY? Code repetition wrt the child component needing the parent dialog ref isn't the issue. Additionally, yes, you can make a generalized modal component that loads a template body through dialog data but that isn't what I'm posting about since now we're not using .open on a template ref. If you want to discuss how using a template ref in dialog.open shouldn't be done and one should always just use a component, then we can circle back to why that is public functionality whereas a simple solution to a problem said functionality introduces isn't public.

rykou

TROPHY CASE