Did you know that it is rather easy to setup a VM to test your NixOs configuration?
# flake.nix
{
inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";| package main | |
| import ( | |
| "html/template" | |
| "net/http" | |
| "strconv" | |
| ) | |
| /*********************** | |
| This is a simple demonstration of how to use the built-in template package in Go to implement |
| vim.g.mapleader = "," | |
| vim.opt.filetype="on" | |
| vim.opt.filetype.indent="on" | |
| vim.opt.filetype.plugin="on" | |
| vim.opt.encoding="utf-8" | |
| vim.opt.syntax="on" | |
| vim.opt.compatible=false |
Run NixOS ISO using Apple Virtualization framework (for example UTM)
hdiutil mount *.isocp /Volumes/nixos-minimal-2?/boot/{Image,initrd} ..less /Volumes/nixos-minimal-2?/EFI/boot/grub.cfgconsole=hvc0 to params.| IAM Permission | Params | |
|---|---|---|
| amplify:CreateApp | iamServiceRoleArn | |
| amplify:UpdateApp | iamServiceRoleArn | |
| appconfig:CreateConfigurationProfile | RetrievalRoleArn | |
| appconfig:UpdateConfigurationProfile | RetrievalRoleArn | |
| appflow:CreateConnectorProfile | connectorProfileConfig.connectorProfileProperties.Redshift.roleArn | |
| appflow:UpdateConnectorProfile | connectorProfileConfig.connectorProfileProperties.Redshift.roleArn | |
| application-autoscaling:RegisterScalableTarget | RoleARN | |
| apprunner:CreateService | SourceConfiguration.AuthenticationConfiguration.AccessRoleArn|InstanceConfiguration.InstanceRoleArn | |
| apprunner:UpdateService | SourceConfiguration.AuthenticationConfiguration.AccessRoleArn|InstanceConfiguration.InstanceRoleArn |
| # ~/.bashrc: executed by bash(1) for non-login shells. | |
| # If file exists (likely) copy fragment below into existing script: | |
| # If stdin is a terminal | |
| if [ -t 0 ]; then | |
| # Set GPG_TTY so gpg-agent knows where to prompt. See gpg-agent(1) | |
| export GPG_TTY="$(tty)" | |
| # Set PINENTRY_USER_DATA so pinentry-auto knows to present a text UI. | |
| export PINENTRY_USER_DATA=USE_TTY=1 |
I'm going to walk you through the steps for setting up a AWS Lambda to talk to the internet and a VPC. Let's dive in.
So it might be really unintuitive at first but lambda functions have three states.
An example that shows the difference between creating a JavaScript class and subclass in ES5 and ES6.
| # | |
| # Bucket doesn't exist yet, run terraform plan | |
| # | |
| $ terraform plan | |
| Refreshing Terraform state prior to plan... | |
| The Terraform execution plan has been generated and is shown below. | |
| Resources are shown in alphabetical order for quick scanning. Green resources | |
| will be created (or destroyed and then created if an existing resource |
| var Col = require('react-bootstrap/lib/Col') | |
| var PageHeader = require('react-bootstrap/lib/PageHeader') | |
| var React = require('react') | |
| var Row = require('react-bootstrap/lib/Row') | |
| var {connect} = require('react-redux') | |
| var {reduxForm} = require('redux-form') | |
| var DateInput = require('./DateInput') | |
| var FormField = require('./FormField') | |
| var LoadingButton = require('./LoadingButton') |