Lamby v4, Dev Containers, & More! (#21)

Author: metaskills

.devcontainer/Dockerfile

@@ -0,0 +1 @@
+FROM ruby:3.1-bullseye

.devcontainer/devcontainer.json

@@ -0,0 +1,10 @@
+{
+  "build": {
+    "dockerfile": "Dockerfile"
+  },
+  "features": {
+    "ghcr.io/devcontainers/features/common-utils": {},
+    "ghcr.io/devcontainers/features/sshd:latest": {}
+  },
+  "remoteUser": "vscode"
+}

Dockerfile

@@ -1,54 +1,42 @@
 # Lamby Cookiecutter
 
-<a href="https://lamby.custominktech.com"><img src="https://user-images.githubusercontent.com/2381/59363668-89edeb80-8d03-11e9-9985-2ce14361b7e3.png" alt="Lamby: Simple Rails & AWS Lambda Integration using Rack." align="right" width="300" /></a>
+<a href="https://lamby.custominktech.com"><img src="https://raw.githubusercontent.com/customink/lamby/master/images/social2.png" alt="Lamby: Simple Rails & AWS Lambda Integration using Rack." align="right" width="450" style="margin-left:1rem;margin-bottom:1rem;" /></a>
 
 An [AWS SAM cookiecutter](https://technology.customink.com/blog/2020/03/13/using-aws-sam-cookiecutter-project-templates-to-kickstart-your-ambda-projects/) project template to quickly create a new Rails application for AWS Lambda. Details:
 
-- Rails v6.x on Ruby 2.7 runtime.
-- Integrated JavaScript development.
-- Compiles CSS/JS assets.
-- No ActiveRecord. Read our [Database Options](https://lamby.custominktech.com/docs/database_options) guides.
+- Rails v7.x on Ruby 3.1 runtime.
+- Integrated JavaScript & CSS Development.
+- CI/CD GitHub Actions for Test & Deploy.
 
 **[Lamby: Simple Rails & AWS Lambda Integration using Rack.](https://lamby.custominktech.com)**
 
 ## Usage
 
-⚠️ Please reference the full [Quick Start](https://lamby.custominktech.com/docs/quick_start) guide on the Lamby site for details. Basic usage is:
-
-### SAM Init
-
-If you have the [AWS SAM CLI](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/what-is-sam.html) already installed, use the first command. If not, use the second Docker based command.
-
-```shell
-$ sam init --location "gh:customink/lamby-cookiecutter"
-```
+⚠️ Please reference the full [Quick Start](https://lamby.custominktech.com/docs/quick_start) guide on the Lamby site for details. Basic usage requires Docker to be installed to run the Cookiecutter software using the following command.
 
 ```shell
 $ docker run \
   --rm \
   --interactive \
   --volume "${PWD}:/var/task" \
-  public.ecr.aws/sam/build-ruby2.7 \
-  sam init --location "gh:customink/lamby-cookiecutter"
-```
-
-### Setup & Deploy (within project)
-
-```shell
-$ ./bin/bootstrap
-$ ./bin/setup
-$ ./bin/deploy
+  ghcr.io/customink/lamby-cookiecutter \
+  "gh:customink/lamby-cookiecutter"
 ```
 
 ## Contributing
 
-This starter project is 100% scripted within Docker using the scripts in the `bin` directory. To build run the following commands.
+This project is built for [GitHub Codespcaes](https://github.com/features/codespaces) using the [Development Container](https://containers.dev) specification. Once you have the repo cloned and setup with a dev container using either Codespaces or [VS Code](#using-vs-code), run the following commands. This will install Rails and build the Cookiecutter project with any local changes.
 
 ```shell
-./bin/bootstrap
-./bin/build
+$ ./bin/build
 ```
 
+#### Using VS Code
+
+If you have the [Visual Studio Code Dev Container](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) extension installed you can easily clone this repo locally, use the "Open Folder in Container..." command. This allows you to use the integrated terminal for the command above.
+
 ## Code of Conduct
 
 Everyone interacting in the Lamby project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/customink/lamby/blob/master/CODE_OF_CONDUCT.md).
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/customink/lamby. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.

README.md

@@ -1,6 +1,7 @@
 #!/bin/sh
 set -e
 
-docker-compose run \
-  build \
-  ./bin/_build
+./bin/rails-new
+./bin/lambify
+./bin/inserts
+./bin/cleanup

bin/_build

@@ -7,6 +7,7 @@ PROJECT_FOLDER="{{cookiecutter.project_name}}"
 cd $PROJECT_FOLDER
 
 rm -rf ./.git \
+       ./config/puma \
        ./config/master.key \
        ./config/credentials.yml.enc \
        ./Gemfile.lock \

bin/_lambify

@@ -13,11 +13,21 @@ insert_file_over_pattern () {
   sed --in-place "${rline}r ../inserts/${1}" $1
 }
 
-# Replace `RenameMe` module namespace with cookiecutter's name.
+# We are leaning into dev containers. More: https://containers.dev
+#
+cp -r ../inserts/.devcontainer .
+
+# Replace RenameMe|rename_me with cookiecutter's name.
 #
 sed --in-place \
   's/RenameMe/{% include "_cctmp\/class_name.txt" %}/' \
   config/application.rb
+sed --in-place \
+  's/rename_me_production/{% include "_cctmp\/dash_name.txt" %}-production/' \
+  config/cable.yml
+sed --in-place \
+  's/rename_me_production/{% include "_cctmp\/dash_name.txt" %}-production/' \
+  config/environments/production.rb
 
 # Create a simple welcome to Lamby/Rails index page. To do
 # this we need a simple starter route, view layout and template.