CodeHiRise (@codehirise) profile picture

Wander in the wonderful world of electronics, web dev and in between

linux server
Joined January 2023
Photo by CodeHiRise (@codehirise)Photo by CodeHiRise (@codehirise)Photo by CodeHiRise (@codehirise)Photo by CodeHiRise (@codehirise)Photo by CodeHiRise (@codehirise)Photo by CodeHiRise (@codehirise)
CodeHiRise retweeted
Replying to @JeremyDeceuster
Yep, that works as a lightweight local guardrail. It makes Socket Firewall the default path for everyday installs. For macOS/Linux users, the equivalent in zsh/bash would be: alias npm="sfw npm" alias yarn="sfw yarn" alias pnpm="sfw pnpm" alias pip="sfw pip" alias uv="sfw uv" alias cargo="sfw cargo"
7
6
1
101
8,608
Day 7 of 7 cloud best practices that can save your production launch 👇 7/7 Tag your cloud resources early. Every resource should have tags like: • Environment • Service name • Owner • Cost center Untagged infrastructure becomes impossible to track as systems grow. #devops
28
Spent a few hours debugging a Next.js app on ECS Service Connect failing health check. Turns out I missed setting HOSTNAME=0.0.0.0 in task definition env vars 🤦‍♂️ #nextjs #aws #devops
41
Day 6 of 7 cloud best practices that can save your production launch 👇 6/7 Use Infrastructure as Code from day one. Manual cloud changes feel fast early on Until nobody remembers: • What changed • Who changed it • Why it changed #terraform #iac #cloud #devops #aws
1
47
That’s how cloud environments turn into unmanageable snowflakes. With Infrastructure as Code everything is version controlled and reproducible down to the exact state. This makes environment provisioning and management far more predictable.
1
23
Try using iac tools like Terraform/Pulumi for your next project. @HashiCorp @PulumiCorp #terraform #pulumi
33
Day 5 of 7 cloud best practices that can save your production launch 👇 5/7 Never hardcode environment-specific values into your application. Things like: • Bucket names • Queue URLs • Regions • API endpoints • Database hosts
1
28
These values should live in configs, secrets managers, or environment variables not inside your codebase. This will make sure we can easily swap them without costly database backfills. #cloud #devops #software #development #aws
40
Day 4 of 7 cloud best practices that can save your production launch 👇 4/7 Not every workload belongs on Spot instances. Spot is great for: • Batch jobs • Background workers • Temporary workloads If interruption is acceptable, Spot can massively reduce cloud costs.
1
22
But do not run critical customer-facing systems or stateful apps like databases on infrastructure that can disappear with little warning. Before using Spot ask: “What happens if this server vanishes in 30 seconds?” Cheap infrastructure becomes very expensive during outages.
22
Day 3 of 7 cloud best practices that can save your production launch 👇 3/7 Keep your ingress and egress IPs predictable. These are the main entryways and exits to your environment.
1
39
Randomly changing outbound IPs will eventually break: • Third-party integrations • Firewall rules • Webhooks • Enterprise whitelisting Static IPs save a surprising amount of operational pain later.
27
Day 2 of 7 cloud best practices that can save your production launch 👇 2/7 Do not put everything in public subnets. Your databases, services, queues, and private workloads should never be directly exposed to the internet. Public access should be intentional, not the default
1
31
Use: • Public subnets for load balancers and nat gateways • Private subnets for applications and databases A single misconfigured security group should not expose your entire infrastructure. Good network isolation makes your infrastructure secure and keep things organized.
22
Day 1 of 7 cloud best practices that can save your production launch 👇 1/7 Never deploy directly to production first. Ship to a staging environment that mirrors production as closely as possible: • Same services • Same versions • Same network setup
1
29
Most “it worked on staging” disasters happen because staging was never actually production-like. Your staging environment does NOT need to match production scale. Scale it down to save cost, but keep the architecture and configurations consistent.
28
Fun fact 👾 Did you know your PC is secretly a giant heater? It draws electricity and converts all of it into heat while processing data. That’s the First Law of Thermodynamics in action! 🔥💻 #science #physics
28