DevOps tools
10 browser-based tools for infrastructure and deployment workflows — lint, format, validate, and build config files without uploading anything. No signup, no cloud, nothing leaves your device.
DevOps tools
-
Dockerfile 檢查器
檢查 Dockerfile 的常見錯誤、安全問題與最佳實踐違規。
開啟工具 →
-
NGINX 設定格式化
格式化並縮排 NGINX 設定檔,提升可讀性。
開啟工具 →
-
.env 格式化工具
驗證、排序並格式化 .env 環境變數檔案。
開啟工具 →
-
.htaccess 建立器
產生 Apache .htaccess 規則,支援重新導向、HTTPS、認證等設定。
開啟工具 →
-
GitHub Actions 檢查器
驗證 GitHub Actions 工作流程 YAML 的結構與常見錯誤。
開啟工具 →
-
SSH 金鑰指令建立器
為 RSA、Ed25519 或 ECDSA 金鑰產生合適的 ssh-keygen 指令。
開啟工具 →
-
連接埠參考表
瀏覽並搜尋常見連接埠號,附協定與服務說明。
開啟工具 →
-
SSL 憑證解碼器
在瀏覽器中貼上 PEM 憑證,解碼主體、簽發者與有效期。
開啟工具 →
-
DNS 記錄建立器
建立並格式化 A、AAAA、CNAME、MX、TXT 等 DNS 區域檔記錄。
開啟工具 →
-
.gitignore 建立器
選擇程式語言與框架,產生整合的 .gitignore 檔案。
開啟工具 →
Why browser-only DevOps tools?
Infrastructure configuration files often contain sensitive data: environment variable values, SSL private key paths, server hostnames, and authentication credentials. Uploading these to an online linter or formatter means trusting a third party with production secrets. The tools on this page run entirely in your browser — paste freely, audit thoroughly, and share nothing.
These tools are designed for the moments between commits: quickly checking a Dockerfile before pushing an image, formatting an NGINX config block before a deploy, or building a DNS record string before updating your zone file. Fast, private, and always available.
Choosing the right tool
For container workflows: start with the Dockerfile Linter to catch mistakes before building. For web server work: use the NGINX Formatter or .htaccess Builder. For CI/CD: validate your pipelines with the GitHub Actions Linter. For security: decode SSL certificates or generate SSH keygen commands. For DNS: use the DNS Record Builder. For project setup: generate .gitignore files and format .env files.
常見問題
- Do my config files get uploaded to a server?
- No. Every DevOps tool on this page runs entirely in your browser using JavaScript. Your Dockerfiles, NGINX configs, SSH keys, and certificates never leave your device — not even temporarily.
- Can I use these tools with sensitive production config?
- Yes. Because all processing happens locally in your browser, it is safe to paste production configuration files, SSH key comments, SSL certificates, and .env files without risking exposure to third parties.
- Does the Dockerfile linter cover all best practices?
- The Dockerfile linter checks for the most impactful best practices: correct instruction order, combined RUN statements, avoiding the latest tag, using COPY over ADD, setting a non-root USER, and more. For a comprehensive audit, pair it with Hadolint in CI.
- Can the SSL cert decoder handle certificates from any CA?
- Yes. The decoder parses the PEM-encoded DER binary directly in your browser. It works with certificates from any Certificate Authority — Let's Encrypt, DigiCert, Comodo, self-signed, or any other CA.
- What DNS record types does the DNS Record Builder support?
- The builder supports A, AAAA, CNAME, MX, TXT, NS, CAA, and SRV records. It outputs the zone file format and the matching dig command for verification.
- Which .gitignore templates are included?
- Templates cover the most common stacks: Node.js, Python, Java, Go, Rust, PHP, Ruby, .NET/C#, Xcode/iOS, Android, React, Docker, Terraform, and a generic OS template for macOS and Windows system files.
- Do these tools work offline?
- Yes. All computation runs locally once the page has loaded. The tools continue to work with no network connection after the initial page load.
- Which SSH key type should I generate?
- Ed25519 is the modern default — it is fast, small, and secure. Use RSA 4096 when connecting to older servers that do not support Ed25519. Avoid RSA 1024 and DSA entirely as both are considered weak.