dotfiles
securestore-rs
| dotfiles | securestore-rs | |
|---|---|---|
| 4 | 3 | |
| - | 112 | |
| - | 0.9% | |
| - | 5.1 | |
| - | 2 months ago | |
| Rust | ||
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dotfiles
-
Let the (terminal) bells ring out
Source: https://github.com/susam/dotfiles/blob/main/shrc#L381
-
How I run my servers
I have a similar setup for my personal and project websites. Some similarities and differences:
* I use Linode VMs ($5/month).
* I too use Debian GNU/Linux.
* The initial configuration of the VM is coded as a shell script: https://github.com/susam/dotfiles/blob/main/linode.sh
* Project-specific or service-specific configuration is coded as individual Makefiles. This takes care of creatng An example: https://github.com/susam/susam.net/blob/main/Makefile
* The software is written in Common Lisp. In case of a personal website or blog, a static website is generated by a Common Lisp program. In case of an online service or web application, the service is written as a Common Lisp program that uses Hunchentoot to process HTTP requests and return HTTP responses.
* I use Nginx too. Nginx serves the static files as well as functions as a reverse proxy when there are backend services involved. Indeed TLS termination is an important benefit it offers. Other benefits include rate limiting requests, configuring an allowlist for HTTP headers to protect the backend service, etc.
-
My Favorite Commandline Oneliners
I have something similar but a little more elaborate at my ~/bin to ensure that there isn't a severe loss of quality during the conversion: https://github.com/susam/dotfiles/blob/e434b7c/bin/xmp3
-
Using GNU Stow to manage your dotfiles (2012)
I follow a similar but handcrafted approach. I have a dotfiles repo with a setup script that automates the creation or deletion of all the symbolic links: https://github.com/susam/dotfiles/blob/master/setup
So what I do on any new system is just:
git clone https://github.com/susam/dotfiles.git
securestore-rs
-
Ask HN: Are there any open source forks of nomad smd consul?
We use and maintain this cross-platform/cross-lang secrets management option: https://github.com/neosmart/securestore-rs
It keeps secrets out of your environment variables and lets you manage secrets the same way you do code (in lock-step with the code that uses it and as easy to update a secret just by pushing to git), but it's definitely for smaller teams or projects.
-
How I run my servers
You can include encrypted secrets and deploy the key out of band. Our open source solution for this (cross-platform, cross-language): https://neosmart.net/blog/securestore-open-secrets-format/
Eg this is the rust version on GitHub: https://github.com/neosmart/securestore-rs/tree/master
- Secure Store
What are some alternatives?
bashdot - Minimalist dotfile management framework.
docker-rollout - 🚀 Zero Downtime Deployment for Docker Compose
dotfiles - Settings for various tools I use.
ts-neural-network - A neural network to play with
nix - my nix modules, overlays, host configurations, and more!
Exocryption - A simple file encryption program written in Rust using the Rust Crypto set of crates.
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
susam.net - Source code of https://susam.net/
etsd - Transmit sensitive data encrypted across your organization!
ShellCheck - ShellCheck, a static analysis tool for shell scripts
flyctl - Command line tools for fly.io services