import { Hono } from "hono";
import PDFDocument from "pdfkit";
const app = new Hono();
# -------------------------------------------------------------------------------------------- | |
# Mostly Erlang - episode 019 Elixir With José Valim / October 7, 2013 | |
# | |
# guests: | |
# - Joe Armstrong (@joeerl) | |
# - Robert Virding (@rvirding) | |
# - Jose Valim (@josevalim) | |
# - Fred Hebert (@mononcqc) | |
# - Eric Merit (@ericbmerritt) | |
# |
This is a guide to configure React Native to be built for native and web platforms with Typescript, Vite.js and Storybook support for modelling components.
.terraform/ | |
*.pem | |
*.tf | |
*.tfstate | |
*.yaml | |
*.backup | |
istio-*/ | |
cert-manager-*/ | |
*.swp | |
env |
I am not responsible for any damages, loss of data, system corruption, or any other mishap you may somehow cause by following this guide.
This is mainly a step-by-step reminder/log for myself of how I installed Arch on my laptop. I am putting this out there in case it is useful for someone else, it is not intended to be an official guide. As a result, you may find that this guide is very tedious or lists a lot of unnecessary/intuitive steps or just straight up does things in a way that is considered bad practice. Apart from the latter, this is intentional, as I did not find these steps intuitive at all when
# to run: | |
# > elixir --no-halt udp_server.exs | |
# to test: | |
# > echo "hello world" | nc -u -w0 localhost 2052 | |
# > echo "quit" | nc -u -w0 localhost 2052 | |
# Let's call our module "UDPServer" | |
defmodule UDPServer do | |
# Our module is going to use the DSL (Domain Specific Language) for Gen(eric) Servers | |
use GenServer |
This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.
For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
- By Edmond Lau
- Highly Recommended 👍
- http://www.theeffectiveengineer.com/
=============================================== | |
Dell Display Manager | |
=============================================== | |
Command language | |
----------------------------------- | |
A rich and flexible command language is supported via the | |
command-line, and command-line arguments can be combined. | |
Where appropriate, a specific display can be targeted by | |
prefacing the command with the display number, e.g., |
Worked 2015-09-08 for Phoenix 1.0.1 on Dokku 0.3.25.
These instructions assume you've set up Dokku. If not, go find a tutorial for that part. My notes for setting it up on Digital Ocean.
Create a Dokku app: