Have you ever faced the problem: your PR on github is not merged because you didn’t follow the project style-guide? Or your IDE is reformatting the whole file when you just want to modify one line? We had some of theses problems with our own code-base here at Wanari (most of the time when we […]
By Barnabás Oláh
When we started to you use Slick for the first time, we had no clue on how to set up our code for multiple database types in our Play! application.
I was working on a Play! Framework project and I was wondering why our whole API was available in one piece. It got me thinking whether there is a way to hide at least some parts of the API from the clients. Precisely because some of the clients didn’t have the privilege/permission to execute given operations, e.g. visiting restricted pages. I thought there should be a way to hide at least the operations that are on these restricted pages. I’ve found a way to do so and below it is.
We wanted to deploy a Play! framework application to the cloud but we didn’t want to take care of all security updates on a virtual machine. Heroku is very expensive and Amazon has had no suitable solutions for our needs. We decided to go with Windows Azure.