Have you ever felt the pain that comes when your app runs fine on development, but breaks terribly in production? Maybe your CI build has been red for days, but you haven’t had time to figure out how the CI server is misconfigured?
With containers, you can easily rid yourself of such dependency woes. If the app runs in a container on one machine, it will most likely run in the same container on another.
Once you’ve bought into a container-based development workflow, the question soon arises: how can I get my production server to run my application in a container without the difficulty of having to provision a bare server with all of the other services, writing deploy tasks, and handling scaling issues on my own? In short, can I have a managed production environment that also supports containers?
The answer is yes. Using Deis, an open source Platform as a Service, you can host and manage your Docker-based application using your own Amazon Web Services (AWS) servers, without the hassle of configuring a bare Linux server.
I recently deployed a simple Rails app to Deis, and took notes along the way. In this post, I’ll share the steps I took to set up a Deis Pro account and deploy a new application.
As with any development, test-driving features is the way to go in a Flux app. As I’ve been learning this technology, I’ve been collecting some of the less obvious patterns that make testing easier. In this post, we’ll take a look at some of these strategies, to make it easier for you to build the next big thing.
In part one of this miniseries, we talked about the timeline for ES6 rollout, feature compatibility in existing environments and transpilers, and how to get ES6 set up in your build process.
Today, we’ll continue the conversation, looking at some of the easiest places to start using ES6 in a typical front-end Backbone + React project. Even if that's not your stack, read on! There's something for everyone here.
If you want to try out the examples, you can use a sandboxed ES6 environment at ES6 Fiddle.
You've done it! It all started with an idea and two people in your garage. After weeks of coding and tweaking, you've proven that your business idea is the greatest thing since sliced bread. You used the Build, Measure, Learn cycle to find out what your customers want, and you're pretty sure you have a product market fit.
It's time to build your V1. In the post, we'll look at how to take the most important lessons from the information you've gleaned during the MVP stage of your product's lifecycle and apply them to building the first full release of your product.