Has anyone looked at RapidFort's curated libraries as a Chainguard alternative?

We've been evaluating Chainguard libraries as a way to reduce the risk of pulling vulnerable or malicious open-source packages into our builds. It seemed like one of the few established options. That was until I saw that RapidFort recently launched curated libraries as well.



Has anyone had a chance to compare the two yet? I'm interested in how they differ in practice rather than on the marketing pages. Things like package coverage, malware scanning and workflow integration. Also developer experience and ongoing maintenance all matter to us.



Has anyone here evaluated both or decided one was a better fit?

https://redd.it/1vmo871
@r_devops

Tired of juggling WindTerm / Termius / FinalShell — so I made one Rust app that aims for all three

https://github.com/vesaaa/vsterm

|Capability|VsTerm|WindTerm|Termius|FinalShell|MobaXterm|SecureCRT|Xshell|Tabby|
|:-|:-|:-|:-|:-|:-|:-|:-|:-|
|Implementation language|Rust|C/C++|Electron|Java|C++|C++|C++|Electron|
|Max terminal scrollback lines|100k / 500k (Pro)|unlimited|\-|\-|360,000|128,000|\~2.1B|25,000|
|Command-block folding / outline in terminal output|✅|✅|✗|✗|✗|✗|✗|✗|
|Integrated SFTP pane / remote file manager|✅|✅|✅|✅|✅|◐|◐|◐|
|SFTP transfer progress / queue visibility|✅|◐|◐|✅|◐|◐|◐|◐|
|ZMODEM (rz / sz) built in|✅|✅|✗|✅|◐|✅|✅|✅|
|ZMODEM progress surfaced in the app|✅|✅|✗|◐|◐|◐|◐|◐|
|Terminal ↔ file-pane path sync|✅|✗|◐|◐|✗|✗|✗|✗|
|Elevated SFTP that can follow sudo -i / su|✅|✗|✗|✗|✗|✗|✗|✗|
|Route diagram / policy-routing topology|✅|✗|✗|✗|✗|✗|✗|✗|
|Path trace with geo / ASN enrichment|✅|✗|✗|✗|✗|✗|✗|✗|
|Built-in IP quality / reputation checks|✅|✗|✗|✗|✗|✗|✗|✗|
|CPU / memory / storage graphical monitor|✅|◐|✗|✅|✗|✗|✗|✗|
|Connection / socket monitoring panel|✅|✗|✗|◐|✗|✗|✗|✗|
|Connect effects / motion polish|✅|✗|✗|✗|✗|✗|✗|✗|
|Desk pet|✅|✗|✗|✗|✗|✗|✗|✗|

https://redd.it/1vmbzrv
@r_devops

Looking for feedback on first attempt at setting up hosting and CI/CD for a fullstack .NET and React app with PostgreSQL database, hosted on Github using Github Actions.

Hi,

I'm a Senior Software Engineer with 5YOE. I'm upskilling in DevOps and project setup and have been creating this project to learn over the last few weeks. I've set up the project from scratch. Definining the project structure, creating PR pipelines for linting, formatting, typechecking, unit tests and e2e tests (tests with real database).

Over the last few weeks, I've set up the cloud infrastructure on AWS. I first just created an ec2 instance, uploaded the build files and database docker images, installed neccessary packages and ran it on the barebones ec2 to help me understand the fundamentals.

Then I went about setting up a bit more of a mature setup with RDS for the database on a private subnet, ECS Fargate to host the containerised API, using opentofu for IaaC, setting up a deploy pipeline which uploads the new container images, and runs the migrations and deploys the API service. This was quite a steep learning curve for me and I heavily relied on Gemini for a lot of this, but I have gone back over it to make sure I fully understand it. I'd really appreaciate some feedback on my setup. I'd like to know any best practices I could have followed, any big issues with the setup I've done and how I could have done better.


Also, this is just a simple project that I'm going to switch over to self hosting with Coolify on a Hertzner server soon. But I wanted to try setting up as close to a professional setup as I could, with security and CI/CD in mind.

I've done a write up of the infrastructure here
https://github.com/JackMcBride98/DotnetSpotifyPlaylistSearchTool/blob/main/infrastructure/Infrastructure.md all of the terraform files live in the /infrastructure folder.

Here is a rough overview of the architecture (I didnt draw arrows as it got quite messy)

https://preview.redd.it/e296cv2qq3jh1.png?width=732&format=png&auto=webp&s=6028ba035caf0f7292d6c92f52b1c8d37ddbd877

https://redd.it/1vn4tdm
@r_devops

Amazon Q is saving me these days otherwise I will be having a hard time using AWS services

Thank god AWS has Amazon Q otherwise I'll still be having a very hard time even finding the environment variables of a project.

https://redd.it/1vn3ypi
@r_devops

Looking for a good free resource to learn Jenkins properly

I’m new to DevOps and looking for some good free or paid resources to learn Jenkins from the ground up.
I have around 6 years of experience as a Java developer and have used Jenkins at work, but mostly from a user/developer perspective. I’ve triggered jobs and worked with existing pipelines, but I’ve never actually built a pipeline myself or understood what’s happening behind the scenes.
I’d like to learn Jenkins properly, including things like:
How Jenkins works internally
Setting up Jenkins and agents/nodes
Freestyle jobs vs Pipeline
Declarative vs Scripted Pipeline
Jenkinsfile and pipeline stages
How builds are triggered
Credentials and secrets management
Plugins and how they work
Integration with Git, Maven, Docker, etc.
CI/CD concepts and best practices
How Jenkins distributes work to agents
Debugging failed pipelines
What actually happens from a Git commit → Jenkins → build → test → deployment
I’m comfortable with Java and software development, so I’m mainly looking for something that goes beyond a basic “how to install Jenkins” tutorial.
What resources/courses did you find genuinely useful for learning Jenkins end-to-end? Free resources are preferred, but I’m also open to paid courses if they’re really worth it.
Thanks!

https://redd.it/1vna68k
@r_devops

Where should cross-system infrastructure automation stop?

I’m working through a design where each underlying system remains authoritative for its own resources, rather than putting another source of truth above everything.

The wider runtime only decides whether an operation has enough dependency state, readiness and verification to keep moving.

>The case I’m trying to pressure-test is partial execution. Say an operation spans several systems, three parts succeed and one fails. Each individual system may still be healthy, but the overall operation is incomplete.

Would you let the wider workflow block there, or does that eventually become another control layer operators have to fight with?

Interested in examples where this kind of boundary has worked badly in production.

https://redd.it/1vnaws5
@r_devops

Devops job security with AI

Recently saw posts about how AI isn't that good in distributed systems and it gave me validation on my own experience.

When the model isn't dealing with a single codebase, when it has to connect the dots between a db, redis, other cloud infra, k8s that each already have a lot of configuration, it starts to hallucinate and could pretty much put your infra at risk.

I'm not saying you can't make it work, it does work especially on a clean slate, but when there's a lot of existing context it needs a more guidance.

Using AI lets me do 10x what a DevOps engineer could do alone but I don't think the job disappears anytime soon.

https://redd.it/1vnacqq
@r_devops

How would you architect this?

There is a team that wants to develop a user interface so they can deploy resources such as ec2 instances, etc. We already have an automated pipeline that everyone uses and it deploys these resources already. However, they still want their own which is weird. We still have to build it for their new requirement. That's with the approval of the upper management which has already happened. Anyway, we are just devops engineers and we will follow whatever management commands us even if we don't like it.

I was thinking of building an api layer that developers can use(endpoints). They'll call the endpoints on their ui. I haven't decided which to use in the backend api, maybe aws sdk, boto3 or cdk, whatever. Making that work means, we'll have to setup proper IAM role permissions so that those resources they configured in their configuration files will be created. It's almost administrator permission equivalent is what they need.

I don't know if I am being too strict. It's because we've always kept the infra code just within our devops team. This is the first time a developer team would like to deploy their own resources using their own tooling.

How are you doing it? What's your implementation?

https://redd.it/1vnm3qa
@r_devops

How to learn Linux troubleshooting without working with Linux professionally?

Hi guys! I'm a backend engineer with 6+ yoe, trying to transition into a DevOps role.

I know that having a strong Linux foundation is super important for being a good DevOps engineer, and apparently “Linux troubleshooting” is mandatory in most job postings. But to me, “Linux troubleshooting” sounds so broad, so I’m not really sure how to improve this skill.

Is this something you can learn without working with Linux (professionally) on a daily basis? What do you guys recommend to get hands on experience with it?

Also, what about other important topics, such as Linux logs and networking? I’m building a homelab with Proxmox. Is this a good way to get some hands on experience with these topics?

I’d appreciate any thoughts or advice! Thanks.

https://redd.it/1vnq5qi
@r_devops

How do you measure if readers actually understood your technical articles?

Been thinking about this for a while —
page views and time-on-page tell you
about reach but nothing about comprehension.

Did anyone else try adding quizzes or
knowledge checks at the end of tutorials?

I experimented with adding a quiz to my
Kubernetes Operators article. First result:
0% of readers answered Q1 correctly
(what is the primary purpose of Operators)
but 100% got the deployment steps right.

Tells me my foundational explanation
failed but my implementation guide worked.

Has anyone else tried measuring
comprehension rather than just traffic?
What approaches worked?

https://redd.it/1vnta8b
@r_devops

Improving my ci cd flow

Hello all,been working as IT admin, but mostly working around Azure devops. I been enjoying it, this my first job and doing anything related to devops. Studied CS,majored in networking, hate anything with heavy code development.

Rn,the flow at my company is, the devs use 1 branch only, no PR (yes ik). They would push it to our on prem central repo, and from there i will take over. I will do some modification on some files so it can be built in the new agent environment. And then, we have build pipelines,which would produce artifact of the build files, which will be used by another pipeline, i call it the release/installer pipelines, which we wud package them with a software. Then we have the 3rd type, which is zipping installer to our NAS, sends the metadata of the installer to DB, and notification email (formatting done in pipeline too). All via the pipeline. We also have a 2nd agent machine, exclusively for unit testing, but tbh i dont even understand how they work.

Ive been thinking of ways, to incorporate other methods/tools in the flow, but the only one i can fit is"templates". I dont think i can try to include containerization, as our build agent machine, has some software which are licensed.

Any ideas?at some point i want to jump out, as this job is way too comfy, and lacks growth for me

https://redd.it/1vntyvs
@r_devops

What belongs in a production-readiness gate for a small engineering team?

For a small team with a few services, an enterprise checklist can become ceremony without reducing the main risks. My minimum gate would cover a tested rollback, backups with a restore exercise, health and readiness checks, bounded timeouts and retries, an alert owner, log correlation, secret ownership, and a short incident runbook.



I would add load testing or multi-region recovery only when the service’s traffic and recovery target justify them. Which item has prevented a real incident for a small team, and which common checklist item has mostly created busywork?

https://redd.it/1vnxx4v
@r_devops

what’s the ops incident that stumped you the longest?

Building a course around real production incidents instead of the usual “here’s what a pod is” stuff. Currently have 19 scenarios, things like a stateful service losing its volume binding on redeploy, a network policy silently breaking service-to-service calls, memory limits causing kills that only show up under real load.

What’s missing?

Drop the ops problem that stumped you the most, if it’s one you never fully cracked, or took way longer than it should’ve to root-cause. those gaps are exactly what I want this to cover.

Also not looking for docs-answers, more like what broke, why it wasn’t obvious at first, what you actually tried before it clicked.

Thanks.

https://redd.it/1vo0s7t
@r_devops

If you think a green Trivy job means you're covered, you're a fucking idiot

This is not about Trivy, Syft, or Grype or others. They are good tools.

This is about people who wire one scan into CI, get a green check, and claim their dependency security is covered.

You scanned once.

Your build passes today. Tomorrow a new CVE gets published for a dependency already in main. Unless something rescans it, nothing happens. CI stays green. Production keeps running. Nobody knows.

And if you only scan the production image, where are your dev dependencies? Not in the image, obviously. If they are, then you fucked up in a different way.

But they still ran on developer laptops and in CI. A compromised dev dependency can steal credentials or tamper with the build before your precious image even exists.

Then the scanner produces a report. Cool. Who owns the fix, and who checks that it reached production?

The tools did their job. Your process stopped at "report generated."

If you don't rescan after new vulnerability data arrives and track findings until they're fixed, stop saying you're covered.

Or maybe I'm missing something. A CVE lands a week after the merge. What wakes up in your setup, and who owns it?

https://redd.it/1vo1ob2
@r_devops

How does your team do automated deployments to linux devices in the field?

Right now the team is just ssh-ing into all of the devices and it's a huge time sink.

https://redd.it/1vogxlo
@r_devops

How do you actually diagnose a CI integration-test failure when the root cause isn't obvious?

I'm researching a small CI diagnosis agent, but I'm first trying to understand how experienced engineers actually debug these failures.

Suppose an integration test fails in CI and the logs don't immediately reveal the root cause.

What do you normally investigate first?

For example:

CI logs/stack trace
database availability
dependent/third-party service availability
recent code changes
comparison with the previous/last-green build
test/DB data
previous failure history
rerunning the test

More importantly, how do you decide what to investigate next?

For example, if a recent code change touches the function involved in the failing test, what additional evidence would you want before concluding that the code change caused the failure?

I'm particularly interested in your real-world debugging process rather than an ideal CI/CD workflow.

https://redd.it/1vojtkx
@r_devops

How do you test CI pipelines?

Do you create a sample application to test the proper auth, access and everything the runner needs?

And a related sub question. How do you validate gitops changes before they are merged? Regarding FluxCD or ArgoCD.

https://redd.it/1voki1m
@r_devops

NetAudit – CLI tool for network audits that plays nicely with scripts, CI/CD, and monitoring

Disclosure: I'm the creator of NetAudit.

Hey folks,

I've been using various network scanning tools (nmap, ping, etc.) but wanted something more structured, vendor-aware, and easily automatable. So I wrote NetAudit – a Python CLI toolkit for network auditing and diagnostics.

**Key features from a DevOps perspective:**
\- All commands produce structured output (JSON/CSV) and use stdout for results, stderr for logs – perfect for pipelines
\- Exit codes are meaningful, so you can integrate it into monitoring or alerting
\- Configuration via YAML + environment variables (`NETAUDIT_*`)
\- Supports Cisco, Juniper, Arista over SSH – read-only, so safe for production
\- Snapshots and `diff` let you track changes over time (great for change management)
\- Health checks (`doctor`) cover not just ping, but also interface errors, BGP/OSPF, NTP, etc.

**Example – schedule a daily audit and generate HTML report:**
```bash
netaudit doctor 10.0.0.1 \--device --device-type cisco_ios --json > daily_health.json
netaudit report daily_health.json --format html --output /var/www/audit_report.html

Installation is simple:

bash

git clone https://github.com/netforge201/netaudit.git
cd netaudit && ./install.sh

or via pip if you prefer.

I'd be happy to hear how you'd use it in your workflows – feature requests and PRs are very welcome.

Repo: https://github.com/netforge201/netaudit

If you like it, please consider giving it a ⭐ – it really helps with visibility!

Thanks!**Disclosure: I'm the creator of NetAudit.**

Hey folks,

I've been using various network scanning tools (nmap, ping, etc.) but wanted something more structured, vendor-aware, and easily automatable. So I wrote NetAudit – a Python CLI toolkit for network auditing and diagnostics.

**Key features from a DevOps perspective:**
\- All commands produce structured output (JSON/CSV) and use stdout for results, stderr for logs – perfect for pipelines
\- Exit codes are meaningful, so you can integrate it into monitoring or alerting
\- Configuration via YAML + environment variables (`NETAUDIT_*`)
\- Supports Cisco, Juniper, Arista over SSH – read-only, so safe for production
\- Snapshots and `diff` let you track changes over time (great for change management)
\- Health checks (`doctor`) cover not just ping, but also interface errors, BGP/OSPF, NTP, etc.

**Example – schedule a daily audit and generate HTML report:**
```bash
netaudit doctor 10.0.0.1 \--device --device-type cisco_ios --json > daily_health.json
netaudit report daily_health.json --format html --output /var/www/audit_report.htmlInstallation is simple:bash
git clone https://github.com/netforge201/netaudit.git
cd netaudit && ./install.shor via pip if you prefer.I'd be happy to hear how you'd use it in your workflows – feature requests and PRs are very welcome.Repo: https://github.com/netforge201/netauditIf you like it, please consider giving it a ⭐ – it really helps with visibility!Thanks!

https://redd.it/1vocygj
@r_devops