Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Dynamic generated env config #577

Open
mageddo opened this issue Sep 25, 2024 · 0 comments
Open

Feature Request: Dynamic generated env config #577

mageddo opened this issue Sep 25, 2024 · 0 comments
Labels
feature-request Proposal of a new feature/behavior to be implemented, not reviewed by the repo authors yet

Comments

@mageddo
Copy link
Owner

mageddo commented Sep 25, 2024

Summary & Motivation

Dynamic generated envs based on the JSON config file this way there won´t be necessary to create a manual env for every new config exposed at the config file.

Example:

Provide a solver which can solve from previously configured DNS records.
It's will be useful because people can use DPS for static DNS entries instead of use /etc/hosts or something like.

Goals

What is supposed to do in short. (Optional)

Example

A simple, static DNS server

Non-Goals

What people would think it is supposed to do, but it is not? (Optional)

Example

  • Not to implement a full and complex DNS server

Description

Example

Storage

DNS records will be stored at the existing DPS config file.

DNS Records

  • It will have support to A, AAAA and CNAME entries.
  • Also, TTL by record will be supported
@mageddo mageddo added the feature-request Proposal of a new feature/behavior to be implemented, not reviewed by the repo authors yet label Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Proposal of a new feature/behavior to be implemented, not reviewed by the repo authors yet
Projects
None yet
Development

No branches or pull requests

1 participant