Eugene Fedorenko is Writing, Reading, and Traveling
Published at Beanstalk
Today we’re happy to introduce an enhanced and more useful dashboard. Our team uses Beanstalk every day and we felt like the current version needed some love and some key features. And you — our customers — told us the same thing.
Published at DeployBot
This guide explains how to launch a website powered by Craft CMS with a proper development environment and workflow behind it. You’ll set up a local development environment, put Craft theme and config files under version control with Git, create and configure a new DigitalOcean droplet, install Craft on it, and then deploy your theme and configs to a live website with DeployBot.
Published at DeployBot
This guide explains how to compile website assets with Build Tools during deployment. We’ll use Grunt as an example, but everything below can be applied to Gulp or any other Node-based task runner as well.
Published at DeployBot
Have you ever avoided some parts of your website or application just because they are not up to your standards or just got old and dusty? Well, I certainly have! Lately I’ve been looking for excuses to not add any more servers to environments just because choosing a server type was kinda embarrassing:
Published at DeployBot
Today we’re introducing a new dashboard that provides more information and is easier to use than ever before. The old one was getting the job done (most of the time), but was inelegant, missed data critical for understanding recent events, and was pretty hard to scan and digest. After talking to our customers and seeing how we use it ourselves we decided to start from a blank slate and redesign it instead of applying UI band-aids.
Published at DeployBot
Announcing two exciting design improvements that will save you time when setting up and deploying to your servers.
Published at DeployBot
If you have a sharp eye you may have noticed that some things changed in DeployBot this week. We cleaned up and refreshed the design a little bit, so now it’s sparkling and ready for some new amazing features. Below I will go through what we changed.
Published at Beanstalk
Early last year the Beanstalk team started an internal conversation on the best ways for a private team to control code quality and minimize the chance of breaking production code with a “bad" commit. As a small team of developers we are not used to formal processes, so the most natural thing was to see what bigger teams do. I started researching code review processes and tools in various companies and was astonished by how different they can be. In retrospect it makes sense — software built for NASA has a much smaller right for an error than an open source experiment built on the side. Here are a few cases I found the most interesting:
Published at Beanstalk
It’s a beautiful summer here in Philadelphia and our team started to get tired of all the dark brown backgrounds in Beanstalk. So what can be a better time to give it a slight facelift? Those of you with a sharp eye might have noticed that some things changed this morning.
Published at Beanstalk
While working on new inline comments we got slightly carried away and completely redesigned changeset and file pages. This update was a long due as these were one of the oldest parts of Beanstalk.