#buildpacks

[smarttechie]

Containerizing Spring Boot Applications with Buildpacks

Containerizing Spring Boot Applications with Buildpacks

Step 3: I have added a simple controller to test the application once we run the docker container of our Spring Boot app. Below is the controller code.

Step 4: Go to the root folder of the application and run the below command to generate the Docker image. Buildpacks uses the artifact id and version from the pom.xml to choose the Docker image name.

Step 5:Let’s run the created Docker…

View On WordPress

[ngodingkode-blog-blog]

The Power of Buildpacks in a Platform as-a-Service (PaaS)

The Power of Buildpacks in a Platform as-a-Service (PaaS)

uildpacks are the primary method for deploying applications in Stackato. In essence a buildpack is a network-available directory containing a handful of configuration scripts used to set up containers

View On WordPress

[scalingo]

Why are we technology agnostic?

If you’ve ever browsed our ‘Supported Technologies’ page, you may have noticed that we’re are supporting quite a lot of different stacks.

We think it is part of the goals you may expect from a platform like Scalingo. In the era of microservices, you should be free to use the language, the framework and the database which suits your needs the best. Furthermore, all those services should be able to live in the same infrastructure with the same ease of deployment and maintenance on the long term. We achieve this feature through the use of buildpacks.

Buildpacks are open source pieces of technology popularised by Heroku which are used when you git push your code on Scalingo. In fact a buildpack is a set of scripts which detects the language of your application, compiles and installs its dependencies and defines how your application should be started. You can find all our buildpacks on our Github account.

If you need a specific stack which we don’t support natively, you can even write your own custom buildpack which can be completely tailored to your needs. We’ll talk about that more specifically in a following blog post.

[schneems]

Hacking mruby onto Heroku

If you're in the Ruby world, you've likely heard about [mruby](https://github.com/mruby/mruby), [Matz's](http://en.wikipedia.org/wiki/Yukihiro_Matsumoto) latest experimental Ruby implementation. What I bet you didn't know is that you can run mruby on Heroku right now. As a matter of fact you can run just anything on Heroku, as long as it can compile it into a binary on a Linux box. If you're new to mruby, or to compiling binaries take a look at my last article [Try mruby Today](http://rubysource.com/try-mruby-today/). I cover getting mruby up and running on your local machine. If you are already up to speed then follow along as we use [vulcan](https://github.com/heroku/vulcan) to package mruby as binary, wrap it up in a custom [buildpack](http://blog.heroku.com/archives/2012/7/17/buildpacks/) and then launch an app to use mruby on the Heroku cloud. [Continue Reading ...](http://rubysource.com/hacking-mruby-onto-heroku/) ## Yesterday If you missed it yesterday we announced official support for [Ruby 2.0.0 Preview1](http://blog.heroku.com/archives/2012/11/5/ruby-2-preview-on-heroku/), and announced the dates for our developer conference, [Waza 2013](http://blog.heroku.com/archives/2012/11/6/waza-2013/), including the [Waza call for Speakers](http://blog.heroku.com/archives/2012/11/6/waza-2013/).

[raul-b-blog]

Slides which explain perfectly what you could do with Heroku (everything) More info at http://blog.heroku.com/archives/2012/7/17/buildpacks/