Tags
Every topic covered on CME Vietnam Engineering, with the posts under each.
#announcements
-
Welcome to CME Vietnam Engineering
Why this blog exists, what we plan to write down, and a plain note on how these posts are written.
#ci
-
Security Scanning on Free Tools, Now That Finding Bugs Is Cheap
PHP2Shell was found with AI and attacked before its patch shipped. Why that is the new normal, how we built SAST, dependency, secret, IaC and image scanning from free tools, and what a green security check still does not tell...
-
One Spot VM per CI Job, and Everything It Took to Get There
How our GitHub Actions jobs moved from hosted runners to a Linode host, back, to one always-on GCP Spot VM, and finally to a fresh Spot VM for every job in three pools sized from measurements, with the failures behind...
-
What Actually Made Our CI Faster, and What I Threw Away
PR checks went from 8.5 minutes to 3–5. Most of the gain came from one frozen Go cache. A couple of my other ideas cost more than they saved.
#cloudflare
-
Leaving Supabase Storage for GCS, With an Outage in the Middle
Why we chose Supabase, why 5 GB of egress a month stopped being enough, and what it took to move 439 objects and 255 database rows to Google Cloud Storage without a user-visible change.
#cost
-
One Spot VM per CI Job, and Everything It Took to Get There
How our GitHub Actions jobs moved from hosted runners to a Linode host, back, to one always-on GCP Spot VM, and finally to a fresh Spot VM for every job in three pools sized from measurements, with the failures behind...
#github-actions
-
Security Scanning on Free Tools, Now That Finding Bugs Is Cheap
PHP2Shell was found with AI and attacked before its patch shipped. Why that is the new normal, how we built SAST, dependency, secret, IaC and image scanning from free tools, and what a green security check still does not tell...
-
One Spot VM per CI Job, and Everything It Took to Get There
How our GitHub Actions jobs moved from hosted runners to a Linode host, back, to one always-on GCP Spot VM, and finally to a fresh Spot VM for every job in three pools sized from measurements, with the failures behind...
-
What Actually Made Our CI Faster, and What I Threw Away
PR checks went from 8.5 minutes to 3–5. Most of the gain came from one frozen Go cache. A couple of my other ideas cost more than they saved.
#go
-
What Actually Made Our CI Faster, and What I Threw Away
PR checks went from 8.5 minutes to 3–5. Most of the gain came from one frozen Go cache. A couple of my other ideas cost more than they saved.
#google-cloud
-
One Spot VM per CI Job, and Everything It Took to Get There
How our GitHub Actions jobs moved from hosted runners to a Linode host, back, to one always-on GCP Spot VM, and finally to a fresh Spot VM for every job in three pools sized from measurements, with the failures behind...
-
Leaving Supabase Storage for GCS, With an Outage in the Middle
Why we chose Supabase, why 5 GB of egress a month stopped being enough, and what it took to move 439 objects and 255 database rows to Google Cloud Storage without a user-visible change.
#migration
-
Leaving Supabase Storage for GCS, With an Outage in the Middle
Why we chose Supabase, why 5 GB of egress a month stopped being enough, and what it took to move 439 objects and 255 database rows to Google Cloud Storage without a user-visible change.
#security
-
Security Scanning on Free Tools, Now That Finding Bugs Is Cheap
PHP2Shell was found with AI and attacked before its patch shipped. Why that is the new normal, how we built SAST, dependency, secret, IaC and image scanning from free tools, and what a green security check still does not tell...
#storage
-
Leaving Supabase Storage for GCS, With an Outage in the Middle
Why we chose Supabase, why 5 GB of egress a month stopped being enough, and what it took to move 439 objects and 255 database rows to Google Cloud Storage without a user-visible change.
#supply-chain
-
Security Scanning on Free Tools, Now That Finding Bugs Is Cheap
PHP2Shell was found with AI and attacked before its patch shipped. Why that is the new normal, how we built SAST, dependency, secret, IaC and image scanning from free tools, and what a green security check still does not tell...
#testing
-
What Actually Made Our CI Faster, and What I Threw Away
PR checks went from 8.5 minutes to 3–5. Most of the gain came from one frozen Go cache. A couple of my other ideas cost more than they saved.