From f9e1e3a8d172153d5847269ca1343cc4d284c5c0 Mon Sep 17 00:00:00 2001 From: Hannes Mehnert Date: Sun, 10 Apr 2016 15:27:14 +0100 Subject: [PATCH] typo --- Posts/OperatingSystem | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Posts/OperatingSystem b/Posts/OperatingSystem index 96ca3f5..9da17de 100644 --- a/Posts/OperatingSystem +++ b/Posts/OperatingSystem @@ -133,7 +133,7 @@ At compile (configuration) time, the TLS keys are baked into the image, in addit git repository, the IPv4 address and ports the image should use: The full command line for configuring this website is: `mirage configure --no-opam --xen -i Posts -n "full stack engineer" -r https://github.com/hannesm/hannes.nqsb.io.git --dhcp false --net direct --ip 198.167.222.205 --netmask 255.255.255.0 --gateways 198.167.222.1 --tls 443 --port 80`. It relies on the fact that the TLS certificate chain and private key are in the `tls/` subdirectory, which is transformed to code and included in the image (using [crunch](https://github.com/mirage/ocaml-crunch)). An improvement would be to [use an ELF section](https://github.com/mirage/mirage/issues/489), but there is no code yet. -After configuring and installing the required depedencies, a `make` builds the statically linked image. +After configuring and installing the required dependencies, a `make` builds the statically linked image. Deployment is done via `xl create canopy.xl`. The file `canopy.xl` is automatically generated by `mirage --configure` (but might need modifications). It contains the full path to the image, the name of the bridge interface, and how much memory the image can use: