Learning more about Lambda Amazon Linux images:
$ cat /etc/os-release | grep LIKE
ID_LIKE="centos rhel fedora"
$ rpm -E %{rhel}
7
$ cat /proc/version
Linux version 5.4.0-1074-azure (buildd@lcy02-amd64-065) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #77~18.04.1-Ubuntu SMP Wed Mar 30 15:36:02 UTC 2022
| require 'rollbar/rails' | |
| Rollbar.configure do |config| | |
| config.use_async = true | |
| config.async_handler = proc do |payload| | |
| LambdaPunch.push { Rollbar.process_from_async_handler(payload) } | |
| end | |
| end |
| FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:14 | |
| VOLUME [ "/var/lib/docker" ] |
| #!/bin/sh | |
| set -e | |
| if ! [ -x "$(command -v docker)" ]; then | |
| echo "== [Custom Ink Strap Codespaces] installing 'docker' and 'docker-compose'... ==" | |
| URL="https://raw.githubusercontent.com/microsoft/vscode-dev-containers/main/script-library/docker-in-docker-debian.sh" | |
| curl -s $URL | sudo bash /dev/stdin 1> /dev/null | |
| fi |
| const { S3, GetObjectCommand } = require("@aws-sdk/client-s3"); | |
| const S3C = new S3(S3Config.mms()); | |
| response = await S3C.send(new GetObjectCommand(params)); | |
| data = await this.streamToString(response.Body); | |
| async streamToString(stream) { | |
| return new Promise((resolve, reject) => { | |
| const chunks = []; | |
| stream.on("data", (chunk) => chunks.push(chunk)); |
| # In config/environments/production.rb | |
| config.middleware.insert_after ActionDispatch::Static, Rack::Deflater, sync: false |
| - name: Checkout (private actions) | |
| uses: daspn/private-actions-checkout@v2 | |
| with: | |
| actions_list: '["myorg/create-ecr-repo@main"]' | |
| ssh_private_key: ${{ secrets.MYORG_GITHUB_SSH_KEY }} | |
| - name: ECR | |
| uses: ./.github/actions/create-ecr-repo | |
| with: | |
| stage: ${{ github.event.inputs.stage }} | |
| repo-name: myorg/myapp |
Rails was made for servers. From web servers to background jobs, orchestrating the complexity of Rails in our cloud's infrastructure is hard work. We can not Kubernetes our way out of it either. There is a better way...one that is not well understood. With AWS Lambda and event-driven methodologies, we can fundamentally reinvent our beloved framework. It can change, and indeed thrive, without servers.
AWS Lambda is a commoditized compute platform of the future. Deeply integrated within AWS, it allows your Rails architecture to be completely reimagined atop fully managed infrastructure resources like API Gateway, SQS, S3, CloudWatch, VPC NAT Gateways, IAM, and so much more. As we explore Rails on Lambda, a pattern of evaporating concerns will become a common theme.
| AWSTemplateFormatVersion: '2010-09-09' | |
| Transform: AWS::Serverless-2016-10-31 | |
| Description: LambdakiqRail | |
| Parameters: | |
| RailsEnv: | |
| Type: String | |
| Default: staging | |
| AllowedValues: |
| metadata = Rails.root.join 'config', 'myapp_ins-8d2c1e14da9ca2bc.xml' | |
| idpdata = File.read(metadata) | |
| parser = OneLogin::RubySaml::IdpMetadataParser.new | |
| SAML_SETTINGS = parser.parse_to_hash(idpdata) | |
| Rails.application.config.middleware.use OmniAuth::Builder do | |
| provider :saml, SAML_SETTINGS.merge( | |
| issuer: 'myapp' | |
| ) | |
| end |