#direnv

[pocke777-blog]

Get Started fluct (お手軽サーバーレスアーキテクチャ)

はじめに

API Gateway Lambdaを利用するときに複数人で開発するときもやりやすいよう fluctというツールを紹介

事前に準備するもの

IAM Role

コンソール画面のIAM → ロールから新しいロールの作成を選択 https://console.aws.amazon.com/iam/home?region=ap-northeast-1#roles

ロール名の設定：適当なロール名を入呂翁

ロールタイプの選択：AWS Lambdaを選択

AWSLambdaBasicExecutionRoleのロールをつける

ユーザーの作成

コンソール画面のIAM → ユーザーから新規ユーザーの作成を選択 https://console.aws.amazon.com/iam/home?region=ap-northeast-1#users

ユーザー名の入力:適当なユーザー名を選択

ユーザーごとにアクセスキーを生成にチェックが入っていることを確認

ユーザーのセキュリティ認証情報をメモしておく

作成したユーザーを選択

アクセス許可からポリシーのアタッチを選択

PowerUserAccessを選択 (実際はサービスによってポリシーの選択を分ける)

AWSLambdaBasicExecutionRoleもロールにつける

Aws SDK

install

npm install aws-sdk

認証情報を設定

下記のディレクトリにファイルを作成して、アクセスキーとシークレットキーを設定

vim ~/.aws/credentials [default] aws_access_key_id = your_access_key aws_secret_access_key = your_secret_key

Install

fluctをinstall

npm install fluct --global

fluctアプリの作成

ベースとなるファイルを生成

fluct new myapp Created ./myapp Created ./myapp/README.md Created ./myapp/.gitignore Created ./myapp/actions Created ./myapp/actions/.keep Created ./myapp/package.json

アクションの作成

fluct g helloworld Created ./actions/helloworld Created ./actions/helloworld/index.js Created ./actions/helloworld/package.json

APIの作成

actinoのパスを変更

myapp/helloworld/package.json { "name": "helloworld", "private": true, "fluct": { "contentType": "text/html", "httpMethod": "GET", "path": "/helloworld", "statusCode": 200 } }

IAM ROLEの設定 事前に用意したIAM Roleを設定

リージョンの指定も行う

myapp/package.json { "name": "myapp", "private": true, "fluct": { "accountId": "設定したroleのid", "restapiId": null, "roleName": "設定したrole名", "region": "ap-northeast-1" } }

デプロイ

fluct deploy Created zip: ./actions/helloworld/lambda.zip Uploaded function: helloworld Updated endpoint: GET /helloworld Deployed: エンドポイントが表示される

アクセスしてみるとHello Wolrldが表示されます!

番外

aws-sdkはディレクトリごとに環境変数を設定するとユーザーの管理がしやすく便利

install

brew install direnv

環境変数の設定 先のどのmyappのルートディレクトリで操作

direnv edit . export AWS_DEFAULT_PROFILE=myapp export AWS_PROFILE=$AWS_DEFAULT_PROFILE

これで下記のようにcredentialsの設定が可能

vim ~/.aws/credentials [myapp] aws_access_key_id = your_access_key aws_secret_access_key = your_secret_key

[captneckbeard]

docker-machine and direnv

If you have a project whose development environment is based on Docker and uses docker-machine, using direnv could save you some repetitive manual configuration.

I had a bit of trouble figuring this out from scratch (it turned out to actually be deceptively simple), so I’m sharing the envrc here for posterity.

# ignore errors here, which are usually due to machine already running docker-machine start default || true eval $(docker-machine env default) export DOCKER_MACHINE_IP=$(docker-machine ip default)

[halkeye]

direnv is one of the coolest tools ever

direnv is one of the coolest tools ever

I’ve always loved the idea of self contained environments but coming from doing perl and c/c++ a long time ago, I’ve never been able to really pull it off. It wasn’t until I encountered virtualenv for python that I finally got this working properly. I had encountered rvm’s gemsets before that, but they always seemed finicky at best.

I started to have complex vim configs, and bash rcs that tried…

View On WordPress

[homebrewupdates-blog]

direnv version 0.1.65 for OS X

The formula for direnv was recently updated to version 0.1.65.

To install direnv on your Mac, open your Terminal application and run the following commands;

brew update brew install direnv

 The updated formula is as follows:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

require 'formula' class Direnv < Formula homepage 'https://github.com/zimbatm/direnv' url 'https://github.com/zimbatm/direnv/tarball/v0.1.65' md5 'fbcedf4ddd5ae2e2fa1760a4ef4280c6' head 'https://github.com/zimbatm/direnv.git' def install # App and support files live in libexec libexec.install Dir['libexec/*'] # Symlink into bin bin.mkpath ln_s libexec+'direnv', bin+'direnv' end end

Currently direnv has no dependencies in homebrew.

See which packages depend on direnv.