maxs-rose / env-tree Goto Github PK

View Code? Open in Web Editor NEW

4.0 1.0 0.0 2.16 MB

Cloud env file storage

Home Page: https://www.envtree.net

License: GNU General Public License v3.0

JavaScript 1.51% TypeScript 97.57% CSS 0.27% Dockerfile 0.65%

cloud environment-variables nextjs typescript

env-tree's Introduction

Env Tree

A simple system to store, manage, and share .env like files across environments or development teams.

Website

Features

Projects to group configurations together
Projects can be shared with other users allowing easy onboarding of new team members
Configurations can be linked to each other with changes to base configuration being automatically propagated to children
CLI tool to allow easy downloading of configuration files in both general purpose and headless environments
Selfhostable with provided docker image

Example use cases

Running docker images with .env configuration files
If developers work between multiple machines .env settings can be easily stored and transfered between machines
CI environments to pull in settings for each run
On-boarding new team members

Note: When downloading files in .env format values are formatted as written in the UI

Selfhost

Details for hosting on your own infrastructure can be found here

Tech

Next.js
TRPC
Prisma
Turbo Repo

env-tree's People

Contributors

Stargazers

Watchers

env-tree's Issues

Docs - Add documention on CLI usage

Cloud - Add icons to projects

This would make it easier to find projects in the list

Cloud - '/projects' link visible when not logged in

Maybe it should not be visible when users is not logged in?

Option to change project name/description

There should be a new option in the project settings to change/update the project name

Docs - Documentation on public endpoints

Currently public endpoits are:

/api/config

Some documentation should be added on how to call these for those who would like to implement their own way to download secrets eg ad a even or Gradle task

Cloud - Better landing page

Landing page should explain what the project is about and instead of just being blank

Group config values

Add an option when creating a config value to group it with others of a similar type.

When exporting to .env each group can be headed with a comment of the group name

# Group 1
VALUE=1
VALUE_2=2

# Group 2
VALUE_3=3

Add project description option when creating a project

When creating a project currently the text is a placeholder, there should be a second input to allow for a description input

CLI - Insert email and access token into secrets file

The CLI could insert the user's email and access token into the downloaded secrets file with a key something like $$CLOUD_SECRET_EMAIL$$ and $$CLOUD_SECRET_TOKEN$$ to ensure that they should not interfere with any user-defined keys. The CLI would then check the previously downloaded file for the user email and token instead of it being a required argument.

Cloud - Search option on projects screen

Should probably be done locally to reduce db load

Cloud - Audit log for edits

A log of who edited config values, what they did, and possibly an undo option.

This could be at the project level and also show configuration deletes/creations and user additions/removals.

CLI - Merge downloaded files

When downloading a file it would be good if the user had the option to merge the newly downloaded one with the currently existing one in the filesystem.