- Should have node 8.11.3 or later installed
- Should have a new AWS IAM User with full admin privileges
- Should have a text editor installed
- Should have the serverless framework installed
- Should have your AWS credentials configured in serverless
| package main | |
| import ( | |
| "fmt" | |
| "net/http" | |
| "github.com/apex/go-apex" | |
| "github.com/apex/go-apex/proxy" | |
| ) |
| package main | |
| import ( | |
| "io/ioutil" | |
| "log" | |
| "github.com/naoina/toml" | |
| "github.com/naoina/toml/ast" | |
| ) |
| #!/usr/bin/env python | |
| from bs4 import BeautifulSoup | |
| from twilio.rest import TwilioRestClient | |
| import json | |
| import os | |
| import re | |
| import requests | |
| url = 'https://postmates.com/los-angeles' |
| import React, { Component } from "react"; | |
| import express from "express"; | |
| import path from "path"; | |
| import { renderToStream, toNodeStream, streamTemplate } from "rapscallion"; | |
| import { Route, StaticRouter } from "react-router-dom"; | |
| class App extends Component { | |
| render() { | |
| return ( |
Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.
This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would
| // Create a Promise that resolves after ms time | |
| var timer = function(ms) { | |
| return new Promise(resolve => { | |
| setTimeout(resolve, ms); | |
| }); | |
| }; | |
| // Repeatedly generate a number starting | |
| // from 0 after a random amount of time | |
| var source = async function*() { |
I’m struggling with providing sensitive information like a password or api key to a Lambda:
In the AWS docs it says: When you create or update Lambda functions that use environment variables, AWS Lambda encrypts them using the AWS Key Management Service.
But they also mention
Storing Sensitive Information
For sensitive information, such as database passwords, we recommend you use client-side encryption using
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/