The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Node.js shipped security updates this week.
For anyone deploying NestJS with Docker, there’s a small detail worth checking: which Node version is actually running inside your deployed container?
Updating Node on the EC2 host won’t update the runtime packaged inside the image.
My checklist would be: check the running version, update the base image, rebuild, test the critical flows, then deploy with a rollback ready.
Easy maintenance to postpone when everything appears to be working.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
refining and updating a few things on LUCERRÁ
Stay tuned, we might re-launch a few things 👀
way to go!!
From packed boxes to a shipment the client can track.
This TechFoundry IMS demo reuses box details, retrieves UPS rates, creates shipping labels, and keeps tracking connected to the client order. A practical example of the AI and automation workflows we build into business software.
Watch the client shipping demo:
https://www.youtube.com/watch?v=8ohniU08JAA
#AI #Automation #SoftwareDevelopment #Shipping
I like that the shipment stays tied to the client order instead of living in a separate carrier tab. When box details get edited after the UPS rate is retrieved, does the system re-quote before creating the label, or lock the original rate? I'd be curious how you handle that mismatch on the tracking side.