Simple Environment Configuration Management
>bootenv provides a simple service that makes it easy to setup configuration variables from a central server instead of hardcoding the values in configuration files. Wherever you are running software, you probably have to configure it with some precious and very secret private keys.
>bootenv helps you keep those keys out of your code and out of trouble.
Why use bootenv?
Have you ever pushed, by mistake, say… your AWS secret keys to a public GitHub repository, and only realized that when Amazon called and you were owing them $25K already?
No… you wouldn’t do that… probably not. But some colleage of yours might!!!
Keeping configuration keys, passwords or any other sensitive data on your code repository is dangerous.
>bootenv helps you separate your environments’ configuration from the code. By providing a centralized server and ready to use and straight-forward libraries for many languages, you can reduce the risk of security breaches because of unintentionally exposed data.
The just-arrived trainee
>bootenv it’s not only good for running software on servers. Don’t loose time setting up environments for new members of your projects. Sharing passwords and credentials by email or chat is both inefficient and troublesome, not to say dangerous. Have your projects ready for lightning-fast onboarding with as close to zero external configuration needed as possible.
>bootenv makes the onboarding process easier and secure by taking care of providing everyone with the credentials they need without any effort. A read-only, development
>bootenv token can be checked in to source control, if pertinent, or otherwise provided to new commers as the only key they need to get all their project configuration. You can control exactly which keys from your configuration get exported by that token.
Ready for production or anywhere
Deploy to production or staging using only one codebase.
>bootenv helps you set up the configuration securely and with minimal effort. Pair that with our Docker images, and you’ll have a super secure and convinient way of setting up your whole production infrastructure.
Yes, It’s “Dockerized”!
>bootenv provides app.bootenv.com and api.bootenv.com for free for individuals, non-comercial and open source projects, so you can start using it quickly. But
>bootenv is open source (Apache 2.0) and sometimes you want to have more control, so Docker is a great way to deploy
>bootenv in your own servers. It brings all the dependencies needed and the images actually are portable (i.e. anywhere that docker runs, you can run these docker images). There are official images for many popular server platforms so it seemed crazy to not include
>bootenv along with this list.
If you want run
>bootenv-webapp, on your own infrastructure, simply run:
$ docker pull bootenv/bootenv-rest-api $ docker pull bootenv/bootenv-webapp $ docker run -d -P bootenv/bootenv-restapi $ docker run -d -P bootenv/bootenv-webapp
Is all you need to get going with
>bootenv now. (Secretly, we are working on
Docker Compose version!)
Continuous integration / Continuous deployment
Your Jenkins or Travis jobs certainly need to be configured as well. Use
>bootenv to set up the enviroment variables, or any other configuration you need so the continuous integration / deployment, works as expected and without having to take risks setting up those precious secret keys by hand.
You can get the values in your environment, for example:
$ curl api.bootenv.com/env/YOUR_SECRET_TOKEN.env | while read line; do export "$line"; done $ echo $MY_VAR some value
Also soon checkout the integrations for Gradle, IntelliJ, Java, Node.js/io.js, Python, Ruby…