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"
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
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
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
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
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
Just published a blog post on cloud production best practices ☁️
Would love to hear your thoughts.
dev.to/codehirise/going-prod…
#cloud #devops #aws #security
@ThePracticalDev @awscloud
1
95
CodeHiRise retweeted
We just shipped the biggest Umami release ever.
Session replay. Custom dashboards. Web Vitals. Advanced filters. All open source.
v3.1 👇
github.com/umami-software/um…
Find latest post 🤖
How to Grant Temporary Read-Only Access to a Kubernetes Cluster codehirise.com/post/how-to-g… #Kubernetes #DevOps #Security
36


