chef-server-nginx

chef-server-nginx is an integration/configuration package intended to run an Opscode/Chef Server behind Nginx as a reverse proxy. It typically provides Nginx configuration and supporting setup to route external HTTPS traffic to the Chef Server components, including required headers and web UI/API routing.

Evaluated Apr 04, 2026 (25d ago)
Homepage ↗ Repo ↗ Infrastructure infrastructure devtools chef nginx reverse-proxy self-hosted
⚙ Agent Friendliness
24
/ 100
Can an agent use this?
🔒 Security
43
/ 100
Is it safe for agents?
⚡ Reliability
28
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
30
Error Messages
0
Auth Simplicity
55
Rate Limits
0

🔒 Security

TLS Enforcement
80
Auth Strength
40
Scope Granularity
0
Dep. Hygiene
35
Secret Handling
60

Security depends heavily on correct Nginx TLS configuration and safe reverse-proxy headers; the package itself is not an auth provider. Misconfiguration can lead to exposure of internal endpoints or degraded transport security. Dependency hygiene cannot be verified from the provided data.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
40
Error Recovery
30
AF Security Reliability

Best When

You are self-hosting Chef Server and want Nginx in front for ingress control, TLS termination, and consistent routing.

Avoid When

You need a fully managed SaaS interface or an SDK/API-only product with documented machine-consumable endpoints; also avoid if you cannot manage reverse-proxy/security configuration carefully.

Use Cases

  • Expose Chef Server (and associated web UI/API endpoints) to clients through a hardened reverse proxy
  • TLS termination and centralized ingress controls at Nginx
  • Custom routing, header normalization, and load-balancing in front of Chef Server

Not For

  • Replacing Chef Server itself (it is not a full Chef Server implementation)
  • Environments that require a turnkey hosted service without self-managed configuration
  • Use cases needing a fully agent-facing API client (this is primarily infrastructure configuration)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: TLS (for transport security) and reverse-proxy forwarding of authenticated requests to Chef Server (Chef-side auth remains the source of truth)
OAuth: No Scopes: No

This package is infrastructure-focused; authentication is not an API-level concern of the package itself but rather handled by Chef Server and client requests passing through Nginx.

Pricing

Free tier: No
Requires CC: No

No hosted pricing information applicable; self-managed open-source/infrastructure configuration.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Reverse-proxy setups can break Chef endpoints if required headers/paths/timeouts are not correctly configured
  • TLS/cert renewal and SNI/hostname matching issues can manifest as application failures
  • Operational behavior depends on Chef Server version and expected upstream configuration

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for chef-server-nginx.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered