How to use Environment Variables on Engine Yard with Envyable

If you're building an application in this day and age, chances are that you're following methods from the Twelve-Factor App. One of these is to store configuration in the environment versus hard-coding them in your application.

With Engine Yard, it's typically recommended that you write some custom Chef to modify your environment. If you’re only dropping in configuration files, like the secrets.yml file that Rails uses, Chef is a bit of an overkill. An easier way is to use the Envyable gem to load environment variables when the application is started.

Before we look at Envyable, let's see some environment variable usage in a typical Rails application.

Read More

Code Reviews on Autopilot: A Quick-Start Guide to Git Reflow

For the past several years, Engine Yard has sponsored the Fukuoka Ruby Awards which highlight interesting projects created with Ruby that help move the industry forward. This year's winner of the Engine Yard award is git reflow, a tool that helps to enforce development best practices.

What is git reflow?

Git reflow is a ruby gem that extends git with a few additional commands to connect with GitHub, BitBucket, or GitHub Enterprise. These commands let you create pull requests from the command line and provide a standardized method of delivering completed branches.

Let's take a closer look at how to use this tool.

Read More
Learn about Engine Yard
Try Engine Yard for your Ruby or PHP Apps

Engine Yard Becomes Founding Corporate Sponsor of Ruby Together

All of the infrastructure used by Ruby developers today, including Bundler, RubyGems, and has been maintained and developed for many years entirely by volunteers. While it's good that no one company controls resources shared by the community, it's terrible that the only people who work on our shared infrastructure are doing so for free, in their spare time.

Ruby Together was founded so the community can cooperate to solve that problem. It will fund on-call rotations, maintenance work, and improvements to the shared, public infrastructure used by the entire Ruby community.

Read More

Engine Yard Joins Forces With OpDemand

Engine Yard has always been dedicated to providing the best possible platform for your production applications. With thousands of deployed applications and happy customers supported by our platform, our success speaks for itself.

The leading edge of technology is not static for long, though. To support our customer's rising adoption of container based solutions, we are pleased to announce that Engine Yard is joining forces with OpDemand, the creator of Deis.

Deis is the leading Docker-native open source platform in use by over 200,000 developers around the world. Join them: download Deis today!

Here’s how the Deis and Engine Yard Platforms fit together to support both Docker container apps in Deis and Ruby on Rails, PHP, and other apps on our curated stacks and services.

With the Deis platform, you can use build packs to run Ruby, Python, Node.js, Java, Clojure, Scala, Play, PHP, Perl, Dart, and Go—as well as any application described in a Dockerfile or Docker Image. Choose the programming language and the tool chain that best suit your needs.

Deis also allows your team to:

  • Decrease spend by sharing server resources
  • Use simple developer-oriented workflows
  • Spin up application containers in seconds
  • Deploy to public, private, and bare metal clouds
  • Bring your application to market quickly and successfully

Engine Yard is dedicated to supporting this critical open source project and we welcome contributions and input from everyone. All of the OpDemand employees will join the Engine Yard team and continue contributing to the open source project.

Engine Yard will continue to run an open roadmap process for Deis and we are committing to contribute major advances to the project in the areas of scheduling, orchestration, and application monitoring.

Our merged teams will bring hard won expertise supporting thousands of applications in production. This means that customers who deploy Docker containers on Deis will be able to immediately access expert support.

Our support plans scale with your needs, from cost-conscious minimal support to robust 24x7x365 proactive support with access to dedicated engineers when needed. With a track record of sustained customer satisfaction levels above 98%, we look forward to helping you scale your applications and business.

Here’s what you can look forward to:

  • A steady stream of innovations in the orchestration of applications from Engine Yard for both container based and Server based applications
  • Rock solid support that backs developers up with superb operational expertise
  • Professional services to help developers scope and build innovative applications that address new markets in record time
  • A company that will do whatever it takes to make customers successful

We’ve got your app. Get started today!

SHA-1 SSL Signatures in Your SSL Certificates

The SHA-1 cryptographic hash algorithm is twenty years old, and the feasibility of collision attacks against it is improving. To combat that threat, Google Chrome will start marking connections as insecure if the website uses a SHA-1 signed SSL certificate.

Starting in version 42 of Chrome, websites using a SHA-1 signed SSL certificate will get a red X across the lock, and users will be notified their connection might not be private. Mozilla plans to make similar changes to Firefox.

Currently, Google Chrome stable is version 41, Chrome Beta is version 42, and Canary builds are version 44. As each stable release of chrome is pushed on six week intervals, the stable version of Chrome is going to be updated to version 42 in the next few weeks.

At this time, only SHA-1 certificates with a validation date expiring after 2015 will be marked as insecure. To stay ahead of the curve, Engine Yard is going to be reaching out to all customers affected by this change.

If you’re doing this on your own, the easiest way to fix this issue is by updating the older certificates to use SHA-2. If interested, you can use a third party to scan your existing certificate for any other shortcomings. Qualys does a pretty good job, as does DigiCert and Symantec.

If you have questions about the security procedures or controls in place at Engine Yard, please do not hesitate to contact us.

You can reach us via our ticketing system or in #engineyard on Freenode.


Look through our specially curated posts to get focused, in-depth information on a single topic.