hst337
SecretVault 
https://github.com/spawnfest/secret_vault
All-in-one solution for storing your secrets inside repository.
Overview
It is a lightweight zero-dependency solution for Elixir projects to store secrets inside your repository that my friend and I made during spawnfest 2022.
Features
-
No external dependencies, pure Elixir
You don’t need to setup and external binaries or services. And you can extend this library in plain Elixir. -
Mix-aware.
Secrets are separated per-environment and there is a bunch of useful mix tasks to manipulate these secrets. Building releases withSecretVaultis nothing different from building regular release. -
Easy to use.
There is a straightforward tutorial for simple installation, and the whole project is well documented. -
Secure.
Uses:crypto’saes256gcmcipher by default. Plus there is a special task for performing very basic but useful audit of your secrets to detect weak or similar passwords.
Sidenote
This project is not available on hex.pm yet, but we’re planning to release a version as a soon as spawnfest evaluation finishes.
Where Next?
Trending in Announcing
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
At WyeWorks, we believe great software is built by combining technical excellence with genuine human connection
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
derpycoder
This is awesome.
derpycoder
I meant it when I said this is awesome!!
Here’s why:
https://github.com/livebook-dev/livebook/issues/1340
LiveBook has this open ticket about storing secret directly on a markdown file, which people generally push to Git repo.
So I was hoping this project of yours fit the bill.
@hst337 please reach out to @josevalim.
hst337
1.0.0 released in hex
Some after-spawnfest fixes were added, documentation, errors and warnings were improved to provide first-class developer experience
https://github.com/SecretVault-elixir/secret_vault
By the way
This project won second place in Spawnfest 2022, and I want to thank organizers and sponsors for the hackaton and generous prizes!
SirWerto
Hello @hst337
Cool project
, just one thing:
When I click on the link under Usage section, I am redirected to a 404 GitHub with the next prompt
Don’t know if it is still on process XD
hst337
Try to click from here: SecretVault v1.2.3 — Documentation
SirWerto
Working!! Thanks
derpycoder
Hey @hst337, congratulations on your win.
Well deserved.
Will it be added to LiveBook, to seamlessly store env secrets directly on .livemd files?
hst337
Not for me to tell
benonymus
Hey,
This seems really cool!
I tried to add it to a project, but I am struggling with some problems.
When I use
SecretVault.Config.fetch_from_current_env/1the returned config is for prod always. If I use fetch_from_env with dev (which is the env I am in) it works.Could you elaborate on practical examples for the library integration?
As a test I tried to put my database password in the vault and use it to start the db.
I followed the docs, and tried to read the value in the
config.exsand in theruntime.exsfiles, but it doesn’t seem to work.How would one go about that? Is that even an intended use case?
Thanks
hst337
Ooh, I am really sorry for this, it is a bug I just forgot to fix. I’ll release patch version right now, and I am still planning add more practical tests during this week
UDP, check out the 1.0.1