WeSearch

I built a self-hosted CI/CD platform with persistent queue, encrypted secrets, and rollback UI — here's what I learned

·4 min read · 0 reactions · 0 comments · 16 views
#devops#opensource#ci/cd
I built a self-hosted CI/CD platform with persistent queue, encrypted secrets, and rollback UI — here's what I learned
TL;DR · WeSearch summary

The article discusses the development of Deploy Center, a self-hosted CI/CD platform designed to simplify deployment processes for small teams. It highlights the architecture choices made, including the use of a persistent queue and encrypted secrets, as well as the implementation of role-based access control. The author shares insights on what worked well and what could be improved in future iterations of the platform.

Key facts
Original article
DEV.to (Top)
Read full at DEV.to (Top) →
Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 2958272) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Sabry Dawood Posted on May 24 I built a self-hosted CI/CD platform with persistent queue, encrypted secrets, and rollback UI — here's what I learned #opensource #devops #typescript #react For the past several months I've been building Deploy Center, a self-hosted CI/CD deployment platform. v3.0 shipped recently, and I want to share the architecture decisions, what worked, and what I'd do differently.

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from DEV.to (Top)