Presets for popular hosting providers

[yamcodes]

Summary

This RFC proposes adding preset configurations for popular hosting services, inspired by T3 Env and Envin.

The goal is to reduce setup friction for common deployment targets while keeping ArkEnv’s core focused and agnostic.

Motivation

Many hosting platforms impose conventions around environment variables (naming, required values, defaults). Presets could help users get started faster and avoid common misconfigurations.

Proposal

Provide opt-in presets for selected hosting providers.

Open question: should these presets live in:

• the core arkenv package, or
• a separate package (e.g. @arkenv/presets)?

Non-goals

• Making presets mandatory
• Hard-coding hosting assumptions into ArkEnv core

Open questions

• Which providers should be included initially?
• How do presets interact with custom schemas?
• How much logic is acceptable outside the core?
• Maintenance expectations

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• CLI tool for dev-time environment variable validation #642

👤 Suggested Assignees

• yamcodes

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[yamcodes]

@aruaycodes would you like to take this?

[aruaycodes]

@aruaycodes would you like to take this?

I will take it