Author Archive

If you’re developing Scala apps and let them be checked by Codacy, you might have enabled the check “Imports should be sorted alphabetically“. What sounds easy, isn’t in fact. Here are my findings, summarised as example imports. I hope this helps someone.. I’m sure, I’ll check back on this page in about a week again….

In an event-sourced environment, you sometimes have to introduce an artificial delay to some actions to make sure read-sides had the time to update themselves. If you’re using the classic routing mechanism with a routes-file, you can add such a delay declaratively, like here: This would delay the response of the update-action by 800 Milliseconds, […]

If you have to create a stored procedure in your PlayFramework Database Evolution Script, make sure to properly escape your semicolons (by using two semicolons):

I recently wanted to play a DVD, where I only had the bare folder structure. KODI is supposed to support this, but its not working yet, so I ended up creating the dvd-image on my server myself. This assumes, that you have stored the VIDEO_TS folder in my_dvd Thanks to Ron999 in the Ubuntu-Forums

Recently, I’ve implemented a Swagger-API with Play. As I’ve published a new version of the API, I wanted to make a CHANGELOG available. So the question was, where to store this file.. a blog or some other external resource felt plainly wrong, so I decided to put it right next to the code.

I have a MacBook Pro 15″ Mid-2015 Retina. It uses a 85W MagSafe 2 Power Adapter, which is emitting max 4.25 Ampere at 20 Volts. According to https://omnicharge.zendesk.com/hc/en-us/articles/115000623608-Step-3-How-to-use-DC-output, that means, I’ll have to configure my OmniCharge to 20V DC Output   To do this: Turn the Omnicharge on Double Click the Power button, Menu appears […]

Zipping a stream with the only element of another stream with Akka Streams

send multipart/form-data with playframework wsClient in scala

Taken from the PlayFramework Google Groups File “conf/routes”: ->      /api                        api.Routes // focus on the big R! ->      /                           website.Routes File “conf/api.routes”: GET    /healthCheck/status     […]

To make sure that your Play! Application binds on an IPv4 Socket in your Docker-Container, add the following to your build.sbt file when running locally, you can also start sbt and tell it to prefer the IPv4 Stack.


top