Open Source Ruby Cloud Services Software

AWS CodeDeploy is a fully managed deployment service that automates software deployments to a variety of compute services such as Amazon EC2, AWS Fargate, AWS Lambda, and your on-premises servers. AWS CodeDeploy makes it easier for you to rapidly release new features, helps you avoid downtime during application deployment, and handles the complexity of updating your applications. You can use AWS CodeDeploy to automate software deployments, eliminating the need for error-prone manual operations. The service scales to match your deployment needs. AWS CodeDeploy fully automates your software deployments, allowing you to deploy reliably and rapidly. You can consistently deploy your application across your development, test, and production environments whether deploying to Amazon EC2, AWS Fargate, AWS Lambda, or your on-premises servers. The service scales with your infrastructure.

A data mapping abstraction over the AWS SDK for Ruby's client for Amazon DynamoDB. This library is currently under development. More features will be added as we approach general availability, and while our initial release has as small of an API surface area as possible, the interface may change before the GA release. We would like to invite you to be a part of the ongoing development of this gem. We welcome your contributions, and would also be happy to hear from you about how you would like to use this gem. Feature requests are welcome. This automatically includes a dependency on the aws-sdk-dynamodb gem (part of the modular version-3 of the AWS SDK for Ruby.

Get started quickly using AWS with the AWS SDK for Ruby. The SDK helps take the complexity out of coding by providing Ruby classes for many AWS services including Amazon S3, Amazon EC2, DynamoDB, and more. The SDK is provided as individual downloadable packages for each AWS service, which include code and documentation. The SDK is also available through Ruby Gems. Version 3 of the AWS SDK for Ruby modularizes the monolithic SDK into service-specific gems, for example, aws-sdk-s3 and aws-sdk-dynamodb. Now each service gem uses strict semantic versioning, along with the benefits of continuous delivery of AWS API updates. With modularization, you can pick and choose which service gems your application or library requires, and update service gems independently of each other. You will need to configure credentials and a region, either in configuration files or environment variables, to make API calls. It is recommended that you provide these via your environment.

Neat is a fluid grid framework with the aim of being easy enough to use out of the box and flexible enough to customize down the road. Neat also works great with Bourbon and Bitters, They are all lightweight and easy to work with so it’s a blast to try them out and see if they’re right for your next project. If you need multiple grids in a single project, you can do this by defining a new map stored within a variable of your choosing. This variable can then be passed directly into any of Neat's mixins. Custom grids are especially useful with grid-media. By defining a media attribute within your custom grid, you are able to easily define gutter width and total column count as well as the breakpoint at which they should activate. Creates collapsed grid object that consumes the gutters of its container, for use in nested layouts.

Whether you need compute, dns, storage, or a multitude of other services, fog provides an accessible entry point and facilitates cross-service compatibility. Just getting started working with cloud resources? You are not alone, and having so many complicated options makes it hard to know where to start. fog delivers the knowledge of cloud experts to you, helping you to bootstrap your cloud usage and guiding you as your own expertise develops. By coding with fog from the start you avoid vendor lock-in and give yourself more flexibility to provide value. Whether you are writing a library, designing software as a service product or just hacking on the weekend this flexibility is a huge boon. With a rapidly expanding community and codebase the advantages of fog just keep coming. Join us and together we will realize the future of cloud computing.

The AWS OpsWorks Cookbooks repository provides the built-in Chef cookbooks used by the now-deprecated AWS OpsWorks Stacks service, a configuration-management and application-deployment service that used Chef (and optionally Puppet) to manage fleets of EC2 instances. These cookbooks implemented standard tasks such as package installation, web server configuration, database setup, Ruby/PHP/Java application deployment, and integration with AWS stack lifecycle events (setup, configure, deploy, shutdown). Customers could use these cookbooks as-is or extend/override them by supplying custom Chef recipes. Although OpsWorks Stacks reached end-of-life in May 2024, the repository remains valuable for teams still running legacy stacks or studying Chef automation patterns in an AWS context. The repository includes multiple branches to support different Chef versions (11.10, 11.4, 0.9) and provides reference implementation of layer recipes, attributes, and templates.