Livin' the technology life.
If you’re more of an OpenShift than Heroku fan, here’s how you can get your SBT-built Java project onto OpenShift. OpenShift has fewer dynos (“gears”) at the free tier (only 3) but they idle after 24 hours instead of 1, …
Hosting your SBT-built Java project on RedHat’s OpenShift platform Read more »
I love Heroku for quickly deploying and testing your applications. The free usage tier makes it no cost for simple applications, and the Git Push To Deploy mechanism is a great way to test your build environment isn’t using cached …
Further to my previous post, turns out we want to install files under /opt/<package>, and the associated config under /etc/<package>. And ideally we don’t want to make the sbt-assembly stage force it’s output to a non-standard directory.
Okay, so I need to build proper RPMs rather than using FPM to create them. Our build toolchain uses SBT to build everything, and utilises sbt-assembly to generate a single executable JAR. Which we then wrap up in an RPM …
Using SBT to create an RPM (detour including Vagrant) Read more »