dokku-letsencrypt
config
Our great sponsors
dokku-letsencrypt | config | |
---|---|---|
9 | 32 | |
1,058 | 6,090 | |
0.7% | 0.3% | |
5.4 | 4.5 | |
11 days ago | 6 months ago | |
Shell | Java | |
MIT License | Apache License 2.0 |
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.
dokku-letsencrypt
-
Self-Hosted Password Manager with Dokku
# plugin installation requires root, hence the user change sudo dokku plugin:install https://github.com/dokku/dokku-letsencrypt.git
-
One tool python webapp deployment: initializes your gitlab repo, installs dokku and your app on your server, deploys your app from gitlab to your server, sets your domain and establishes continuous deployment so that all main commits are automatically deployed. Templates for Django, flask, fastApi
downloads and installs dokku-letsencrypt on server
-
Easily deploy a NestJS app for only 5€ a month (before VAT)
$ sudo dokku plugin:install https://github.com/dokku/dokku-letsencrypt.git $ dokku config:set --global [email protected] $ dokku domains:set app-name your-domain.com $ dokku letsencrypt:enable app-name $ dokku letsencrypt:cron-job --add
-
Deploy Ghost using Dokku
You need SSL certificate for your website. With Dokku you can add it in several ways, using official Let's Encypt plugin, or using your own certificate, or using a Cloudflare SSL. Any of these do, but don't neglect this step.
- Fazendo deploy em produção com Rails, PostgreSQL e Dokku
-
Running a NodeJS app with Postgres in Dokku
There are env vars you need to configure so let’s encrypt knows your email address. The plugin docs are worth reading: https://github.com/dokku/dokku-letsencrypt
-
Deploy your Node.js app without a hassle
# on Dokku host sudo dokku plugin:install https://github.com/dokku/dokku-letsencrypt.git
-
Using Dokku with Let's Encrypt wildcard certificate
Right now (when I wrote this post), there is no wildcard support from dokku-letsencrypt plugin. Luckily, Dokku itself can use certificates from other sources.
-
Deploying server-side Kotlin Ktor applications on Dokku
As you may have noticed, our application is available on our Dokku host now – but only in an unencrypted fashion (note the lack of https in the address bar). Thankfully, we live in the age of LetsEncrypt offering free TLS certificates, and Dokku makes it easy to enable automatic certificate retrieval and setup for our application via the dokku-letsencrypt plugin. I strongly recommend setting up this plugin so that people using our application can enjoy securely encrypted web-traffic. Once installed (see installation and initial setup instructions), we can enable the LetsEncrypt integration for our application with a single command:
config
- Hocon (Human-Optimized Config Object Notation)
-
XML is better than YAML
I don‘t understand why HOCON (https://github.com/lightbend/config/blob/main/HOCON.md) isn‘t used more often (at least for configuration use cases). It‘s a superset of JSON, has comments, multiline strings, optional quotes, replacement syntax. We use it at many places, and it‘s as nice at it can get.
- Toml-bench – Which toml package to use in Python?
- slf4j or System.Logger?
- TOML: Tom's Obvious Minimal Language
-
Ron: Rusty Object Notation
HOCON is a great human-readable alternative to JSON. It's a superset of JSON with lots of cool features that make it both more readable and easier to use.
Here's a rundown of HOCON's main features: https://github.com/lightbend/config#features-of-hocon
-
Spring and scala
"Typesafe Config" is the library generally used to read configuration files in HOCON format, which this library introduced. It's commonly used in essentially OOP/imperative Scala contexts, including Akka and its ecosystem.
-
Make systemd better for Podman with Quadlet
Interesting!
For my own servers I use an internal tool that integrates apps with systemd. You point it at the output of your build system and a config file, and it produces a deb that contains systemd unit files and which registers/starts the server on install/reboot/upgrade, as a regular debian package would. Then it uploads it to the server via sftp and installs it using apt, so dependencies are resolved. As part of the build process it can download and bundle language runtimes (I use it with a JVM), it scans native binaries to find packages that the app should depend on, and you can define your config including package metadata like dependencies and systemd units using the HOCON language [1].
Upshot is you can go from a Gradle or Maven build to a running server with a few lines of config. Oh and it can build debs from any OS, so you can push from macOS and Windows too. If your server needs to depend on e.g. Postgres, you just add that dependency in your config and it'll be up and running after the push.
It also has features to turn on DynamicUser and other sandboxing features. I think I'll experiment with socket activation next, and then bundled BorgBackup.
Net/net it's pretty nice. I haven't tried with containers because many language ecosystems don't seem to really need them for many use cases. If your build tool knows how to download your language runtime and bundle it sans container by just setting up paths correctly, then going without means you can rely on your Linux distribution to keep things up to date with security patches in the background, it means networking works as you'd expect (no accidentally opened firewall ports!) and so on. SystemD knows how to configure resource isolation/cgroups and kernel sandboxing, so if you need those you can just write that into your build config and it's done. Or not, as you wish.
With a deployment tool to automate builds/pushes, systemd to supervise processes and a big beefy dedicated machine to let you scale up, I wonder how much value the container part is really still providing if you don't need the full functionality of Kubernetes.
[1] https://github.com/lightbend/config/blob/main/HOCON.md
-
Introducing JXC: An extensible, expressive data language. It's a drop-in replacement for JSON and supports type annotations, numeric suffixes, base64 strings, and more!
Other similar standards: TOML, HOCON
-
Jsonnet is better than YAML for generating JSON
I've also used HOCON pretty extensively for config, and it is better than both YAML and JSON for config with moderate to high complexity.
What are some alternatives?
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
cfg4j - Modern configuration library for distributed apps written in Java.
dokku-postgres - a postgres plugin for dokku
owner - Get rid of the boilerplate code in properties based configuration.
lucid - AdonisJS SQL ORM. Supports PostgreSQL, MySQL, MSSQL, Redshift, SQLite and many more
dotenv - Loads environment variables from .env for nodejs projects.
gitignore.io - Create useful .gitignore files for your project
dotenv - A twelve-factor configuration (12factor.net/config) library for Java 8+
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
Configur8 - Nano-library which provides the ability to define typesafe (!) configuration templates for applications.
ezinnit - ezinnit initializes your gitlab repository and your server. Your app will be live and commits to main will automatically deploy.
centraldogma - Highly-available version-controlled service configuration repository based on Git, ZooKeeper and HTTP/2