via Using the REST API in Nexus 2.x | TheNEXUS.
I’ve recently received a few questions asking how the deployment of Nexus can be automated as much as is possible by using configuration management tools such as Chef, Puppet, Saltstack, Docker, etc. This is common in a scenario where you may want to set up multiple Nexuses with defined repository structures and pre-installed license keys.
In this and a following post, I’ll point you to resources that will help you do exactly that. The Sonatype engineering team has produced some awesome material on these topics over the years and this is my attempt to collate them into a coherent list. Cheers to my colleagues for providing a hailstorm of links and updated content for this project.
via Chef Happens – Managing Solaris with Chef | Wix Engineering.
Adding Solaris servers to be managed by Chef was the most annoying entry in our Wix.com DevOps backlog for almost a year. We moved our MySQL databases to Solaris more than a year ago. We automate everything, but getting Solaris into the Chef kitchen was not that trivial. There is minimal support for Solaris in Chef, so I have made several additions to Chef which other happy Solaris Chef masters might find useful.
My first challenge in setting up Chef on Solaris was that there is no omnibus installer for Solaris 5.10 x86.
Unfortunately, it takes quite a bit of work to go from a bare Solaris install to one that can install the chef gem. So I’ve written a bootstrap file that does that work for you.
This bootstrap file does the following:
- Adds /opt/csw/lib and /usr/local/lib to the library path (via crle).
- Installs pkgutil from OpenCSW.
- Installs libgcc_s1, coreutils, libssl1_0_0, wget, gsed, binutils and gmake via pkgutil.
- Installs ruby from http://www.sunfreeware.com/ (The ruby from OpenCSW does not work correctly).
- Re-names some files so that ruby can build new gems.
- Installs the ohai and chef gems.
- Adds a patch so that adding users to groups works (see CHEF-3245).
- Creates the initial Chef files.
You can get this bootstrap file from GitHub.
via Creating a Cross-platform Docker Development Environment | via @codeship.
Docker is all the hype these days, and with statements like that, many are wondering how they can get on board and take advantage of whatever it is that makes Docker so popular.
That was us just six months ago when we started playing with Docker and trying to fit it into our processes. After just a few months we knew we liked it and wanted to run apps this way, but we were struggling with some of the Docker development workflow.
As the manager of a development team, I like using the same processes and technologies through the whole lifecycle of our applications. When we were running apps on AWS OpsWorks using Chef to provision servers and deploy applications, we used Vagrant with Chef to run the same recipes locally to build our development environment.
EDIT: Ok so If you WANT to do this this way that’s totally cool but I would absolutely suggest checking out this better post I recently wrote here. This week I have been testing some new tools in our environment that are really going to be pivotal to our local development workflow as well as […]
If you haven’t read Part One of this post then this might not be totally helpful, but feel free to hit the original post or follow along anyway! The objective of this section of the post is to deploy and configure our jenkins pipeline so that we can mimic our production workflow and start loading up the […]
This is a multi-part documentation of how to setup a CI/CD workflow in AWS. Some of the tools that will be used are EC2, Chef, CloudFormation, Jenkins, Rspec, and Apache. If you have questions feel free to leave a comment or track me down on Twitter at @devopshomelab Part 1 – Workstation Setup – The […]
Click to Read: This is a republished guest blog post by Ed Ropple. Ed is a platform engineer with Localytics. His ambition is to enable other software developers to be more productive and less error-prone. You can find his original article here.