FlakM

Setting up qemu VM using nix flakes

Did you know that it is rather easy to setup a VM to test your NixOs configuration?

Create simple flake:

# flake.nix
{
  inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";

MarioCarrion

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

wpiekutowski

Run NixOS ISO using Apple Virtualization framework (for example UTM)

• local: Download ISO
  • 22.05 or build ISO: nix-build -A iso_minimal.aarch64-linux '<nixpkgs/nixos/release.nix>'
  • 22.11 Minimal 64-bit ARM
• local: Mount hdiutil mount *.iso
• local: Copy kernel and initrd: cp /Volumes/nixos-minimal-2?/boot/{Image,initrd} ..
• local: Find and copy kernel params: less /Volumes/nixos-minimal-2?/EFI/boot/grub.cfg
• local: Append console=hvc0 to params.
• UTM: Create a new "drive". 16 GB is comfortable, 64 GB is plenty. Attach to your VM.
• UTM: Attach the ISO.

noamsdahan

kevinoid

# ~/.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

reggi

How to setup AWS lambda function to talk to the internet and VPC

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.

1. No VPC, where it can talk openly to the web, but can't talk to any of your AWS services.
2. VPC, the default setting where the lambda function can talk to your AWS services but can't talk to the web.
3. VPC with NAT, The best of both worlds, AWS services and web.

remarkablemark

JavaScript Classes - ES5 vs ES6

An example that shows the difference between creating a JavaScript class and subclass in ES5 and ES6.

Reference

cornet

#
# 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

insin

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')

chantastic

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't