| name: Elixir CI | |
| on: | |
| push: | |
| branches: [ master ] | |
| pull_request: | |
| branches: [ master ] | |
| env: | |
| MIX_ENV: test |
| #!/bin/bash | |
| #install minergate xfast cli miner v1.7 for ubuntu 18.04 or later (XMR supported) | |
| sudo apt-get update && wget https://minergate.com/download/xfast-ubuntu-cli -O minergate-cli.deb && sudo dpkg -i minergate-cli.deb | |
| #starts miner (4 cores for Monero=xmr) | |
| minergate-cli -user <[email protected]> -xmr 4 |
| name: page-counter | |
| runtime: nodejs | |
| description: A page counter |
| ip=$(curl http://169.254.169.254/latest/meta-data/public-ipv4) | |
| echo "Code Server" | |
| echo "http://$ip:8443" | |
| security_group=$(ec2-metadata -s | cut -d " " -f 2); | |
| aws ec2 authorize-security-group-ingress --group-name $security_group --protocol tcp --port 8443 --cidr 0.0.0.0/0 | |
| version="1.32.0-310" | |
| wget https://github.com/codercom/code-server/releases/download/$version/code-server-$version-linux-x64.tar.gz | |
| tar -xvzf code-server-$version-linux-x64.tar.gz | |
| cd code-server-$version-linux-x64 | |
| chmod +x code-server |
| import * as pulumi from "@pulumi/pulumi"; | |
| import * as aws from "@pulumi/aws"; | |
| import * as awsx from "@pulumi/awsx"; | |
| import * as random from "@pulumi/random"; | |
| // Construct a VPC | |
| const vpc = new awsx.ec2.Vpc("vpc"); | |
| // Create an Aurora Serverless MySQL database | |
| const dbsubnet = new aws.rds.SubnetGroup("dbsubnet", { |
I presume the images are bundled as post resources in the ./images/ folder.
It creates a new version at 5% of its original quality that is fetched in the initial page load. When and if the original image is loaded by the browser it will replace the low quality one.
{{< lazyimg "images/1.jpeg" >}} {{< lazyimg "images/1.jpeg" "caption" >}}
I started with Elixir just a couple weeks after the switch from 1.4 to 1.5, so the bulk of online resources were out of date (or at least resulted in deprecation warnings). This guide is for defining Elixir 1.5 supervised modules.
It's not actually terribly complicated. It's just sometimes unclear from examples what's implemented by the language and what you actually have to implement yourself.
Say we want a supervision tree like this (where each atom is a process):
:a
/ \
| <meta name="description" content="{{ if .IsHome }}{{ .Site.Params.description }}{{ else }}{{ .Description }}{{ end }}"/> | |
| <meta name="robots" content="noodp"/> | |
| <link rel="canonical" href="{{ .Permalink }}" /> | |
| <!-- Twitter Card --> | |
| <meta name="twitter:card" content="summary" /> | |
| <meta name="twitter:description" content="{{ if .IsHome }}{{ .Site.Params.description }}{{ else }}{{ .Description }}{{ end }}" /> | |
| <meta name="twitter:title" content="{{ .Title }}{{ if .IsHome }} - {{ .Site.Params.Tagline }}{{ else }} - {{ .Site.Title }}{{ end }}" /> | |
| <meta name="twitter:site" content="{{ .Site.Params.twitter }}" /> | |
| <meta name="twitter:creator" content="{{ .Site.Params.twitter }}" /> |
