ssh-agent
aws-sam-build-images
ssh-agent | aws-sam-build-images | |
---|---|---|
3 | 1 | |
1,091 | 44 | |
1.8% | - | |
4.6 | 7.9 | |
10 days ago | 10 days ago | |
JavaScript | Python | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ssh-agent
-
Continuous Deployment with GitHub Actions and Kamal
Once the image has been built and pushed, you only need to trigger the deployment using Kamal. We use the webfactory/ssh-agent to establish a connection to our production server. After installing the required Ruby dependencies, it’s only a matter of running Kamal. As the image is already built and pushed, we use the --skip-push flag.
-
Flow to build using Github Actions when having dependencies in multiple private repositories
When using Github Actions, to build projects I have been using the ssh-agent approach (https://github.com/webfactory/ssh-agent), with this means the Cargo.toml looks like this:
-
Getting Started with GitHub Codespaces from a Serverless Perspective
Thankfully when I reached out on Twitter, Jonathan Carter on the Codespaces team, seemed to suggest they may be working on a native SSH integration one day. Till then, here is the solution I came up with. This process address some sequencing issues around devcontainer.json's Lifecycle Scripts and when your Dotfiles are installed. Credit to VS Codes Using SSH Keys guide. Also, some things here are pulled directly from the GitHub Action to setup SSH. Again, thanks to Johnathan Carter for the ideas.
aws-sam-build-images
-
Getting Started with GitHub Codespaces from a Serverless Perspective
If you are into Serverless and AWS Lambda, you may already know that the AWS Serverless Application Model (SAM) CLI makes it easy to leverage their Docker build images as development containers. We do exactly this for our Rails & Lambda projects.
What are some alternatives?
codespaces
webssh2 - Web SSH Client using ssh2, socket.io, xterm.js, and express. webssh webssh2
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
blog-post-workflow - Show your latest blog posts from any sources or StackOverflow activity or Youtube Videos on your GitHub profile/project readme automatically using the RSS feed
vscode-sublime-keybindings - Sublime Text Keymap extension for VS Code
amazon-ecs-run-task - Runs an Amazon ECS task on ECS cluster
container-vending-machine - A container vending machine with Harbor and Stripe for independent software vendors (ISVs) to commercially distribute their software through container images. Alternative to Docker Hub Publisher
redux-cool - Build redux logic, without getting nervous 😬
action-tmate - Debug your GitHub Actions via SSH by using tmate to get access to the runner system itself.