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.
This post will tell you how we use a simple YAML file to insert the initial data (like roles, privileges, admin user, and all the other necessary data) into our database. We use Play! Framework (Java) with Hibernate. The important part is how we make Objects from the YAML description using SnakeYAML (Play framework’s integrated YAML parser) though.
I’ll give you some tricks on how to use YAML easily in order to create the initial data for your 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.
I guess if you are reading this, you are working with web applications or web services. There are a number of posts on the internet that explain what shouldn’t be in a controller or in a model, but I didn’t find any proper summary of what should be in the MVC. So here is this blog post to collect our concepts.
If you have a website on which users can register and login, then you also want to protect your application from attackers. We recommend you to protect your application’s actions not only from attackers, but from users, too. For example, if you want to make a user who can upload Excel files on a specific UI, then that user should neither see other UIs, nor should s/he be allowed to take any other actions.
There are many tutorials and articles describing basic module functionality and how you can build it. These articles sometimes leave blanks of the needed information, so this post will do an in-depth tour of the topic applied in the Play framework. What is a module? In Play framework the modules are small functionality packages. These […]
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.
Here is to establishing the perfect collaboration between backend developers and frontend developers!