poc/crieur
1
0
Fork 0
Code Issues 26 Pull Requests Projects 1 Releases 1 Wiki Activity

Design config #17

New Issue
Open
opened 2021-04-28 03:51:06 +02:00 by koalp · 0 comments
koalp commented 2021-04-28 03:51:06 +02:00
Owner
Copy Link

Currently, the config is done using environment variables.

It could be nice to have several ways to config (system defaults, system), with a layered system.

With this system, it could be nice to be able to autogenerate config reference from rust code. (or generate rust code from config reference)

implementation

It could be done using the rust config crate, but this trait lacks Derive macro to create config from struct.

The config_me carte allows to generate rust config code from reference (toml), but do not have Derive macros.

Currently, the config is done using environment variables. It could be nice to have several ways to config (system defaults, system), with a layered system. With this system, it could be nice to be able to autogenerate config reference from rust code. (or generate rust code from config reference) ### implementation It could be done using the rust [`config` crate](https://github.com/mehcode/config-rs), but this trait lacks Derive macro to create config from struct. The [`config_me` carte](https://github.com/Kixunil/configure_me) allows to generate rust config code from reference (toml), but do not have `Derive` macros.
koalp added this to the v0.x.x - before stabilization milestone 2021-04-28 03:51:06 +02:00
koalp added the
status
review_needed
type
discussion
 labels 2021-04-28 03:51:06 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
  
ci

relative to continuus integration

  
priority
critical
Critical priority

  
priority
high
High priority

  
priority
low
Low priority

  
status
abandonned
Issue is abandonned

  
status
accepted
Issue is accepted

  
status
help_wanted
Help wanted on this issue

  
status
in_progress
Issue in progress

  
status
refused
refused issue

  
status
review_needed
Review is needed

  
type
bug
This is a bug report

  
type
discussion
Discussion about the design of the application

  
type
enhancement
It enhance the project

  
type
question
More information is needed

  
type
refactor
Proposition of code refactoring

No Label
ci
priority
critical
priority
high
priority
low
status
abandonned
status
accepted
status
help_wanted
status
in_progress
status
refused
status
review_needed
type
bug
type
discussion
type
enhancement
type
question
type
refactor
Milestone
Clear milestone
No items
No Milestone
v0.x.x - before stabilization
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: poc/crieur#17
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?