Operations | Monitoring | ITSM | DevOps | Cloud

Cloud 66 offers a range of deployment options for Rails applications, each offering different benefits and trade-offs.

I work on the Solutions Architects team here at Puppet. We are sometimes the first line of defense in solving some of our customers' most challenging or unique problems, and every so often, we see trends in problems that we'd previously considered to be edge cases. For example, cCustomers often ask us two questions: How can we connect external configuration data to Puppet? How can we speed up changing their own configuration for service owners without onboarding them to Git approval processes?

On May 11th, at Intel Vision, Densify won Intel Partner of the year for Software Innovation. This award recognizes the impact of our jointly developed offering: Intel Cloud Optimizer (ICO). <="" a=""> Working with Intel we launched a program for enterprise customers that combines Densify analytics software and Intel expert guidance to help match customer workloads with the cloud instances that enable the best performance at the lowest possible cost.

Since its emergence in the mid-2000s, the cloud computing market has evolved significantly. The benefits of reliability, scalability, and reduced set-up costs have created a demand to fuel an ever-growing range of “as-a-service” offerings, resulting in an option to suit most requirements. But despite the advantages, the question of cloud or on-premise remains valid.

It is always helpful to know which version you are running of some software, even more so when running development versions. So it’s good if software is able to tell you its version, for example by calling it with --version. For release versions, maintaining this information by hand is feasible, but in order for development versions to show exact revision information, you need some automation, otherwise updating it will be forgotten, leaving you with wrong information.