/explore
|
You are here 
|
aarol.dev | ||
| | | | |
haseebmajid.dev
In this article, we will go over how we can self-host our instance of Atuin. A tool we can use to sync our shell history across multiple devices. In the previous article, I showed how you can use the official server. However you may want to run your self-hosted one, so no one can access even the encrypted version of your shell history. We will deploy our instance to fly.io. Why fly.io, its pretty easy to deploy they have a great CLI tool. Also we can get a Postgres database deployed, which we need with Atuin. |
|
| | | | | ||
| | | | |
til.simonwillison.net
Fly makes it surprisingly easy to configure wildcard DNS, such that anything.your-new-domain.dev is served by a single Fly application (which can include multiple instances in multiple regions with global load-balancing). |
|
| | | | | ||
| | | | |
fnordig.de
Personal website of Jan-Erik Rediger |
|
| | | | | ||
| | | | |
fullstackphoenix.com
Let say you app uses a javascript library that needs to interact with your app. For example a LiveView component. That is possible with the built in Phoenix Channels and Phoenix PubSub. |
|
| | | |||
