Posted on Leave a comment

Using Hibernate In Standalone App (without Spring) using MariaDB

So recently I need to set up a quick project to store the results of my crawler in a database. Previously, I would use JDBC for this job. However, with the recent knowledge of Hibernate, why don’t I give it a go?

In this post, I’m going to show you how you can use Hibernate to store entities just like you can with frameworks like Spring but on a standalone app (commandline app/Desktop app such as JavaFX).

The application will save an entity Book into a database called book_db

Quick MariaDB setup

To quickly set up a MariaDB database, I use the following docker-compose file. I use mariadb:10.5 and PHPMyAdmin for easy access to the database. If you prefer, you can skip using PHPMyAdmin and use another version of MariaDB:

version: "3"
    image: mariadb:10.5
    container_name: db
      - MYSQL_DATABASE=speech_db
    restart: always
    - 13308:3306
      - mysql_vol:/var/lib/mysql
    image: phpmyadmin/phpmyadmin
    container_name: phpmyadmin
      - PMA_HOST=db
      - PMA_PORT=3306
    restart: always
      - 18811:80

Now, simply run docker-compose up -d, you have a fully functional MariaDB instance up and running.

Import Hibernates and other convenient libraries using Maven

Here is the dependency section in pom.xml


        <!-- -->



Other than hibernate and MySQL connector, the other are optional.

Create hibernate.cfg.xml to setup database connection

The next step would be to create a hibernate.cfg.xml file to configure the connection to the database. Where should you put this file? It should be under resources directory like I have here:

In this file, you specify the db configuration like so:

<?xml version = "1.0" encoding = "utf-8"?>
<!DOCTYPE hibernate-configuration SYSTEM

        <property name = "hibernate.dialect">

        <property name = "hibernate.connection.driver_class">

        <!-- Assume test is the database name -->

        <property name = "hibernate.connection.url">

        <property name = "hibernate.connection.username">

        <property name = "hibernate.connection.password">

Also, open phpMyadmin and create the following table:

Now the hard part is done. Let’s create some entities and save them to the database.

Actually save an entity to database

Let’s create an entity like this:

package entity;

import lombok.Getter;
import lombok.Setter;

import javax.persistence.*;

@Table(name = "book")
public class Book {
    @Column(name = "id", nullable = false)
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;

    String title;
    String author;
    int pages;


And to save the entity, we need a session, which provided by SessionFactory. Let’s create a class that provides SessionFactory

import entity.Book;
import org.hibernate.SessionFactory;
import org.hibernate.cfg.Configuration;

public class SessionFactoryMaker {
    private static SessionFactory factory;

    private static void configureFactory()
        try {
            factory = new Configuration()
        } catch (Throwable ex) {
            System.err.println("Failed to create sessionFactory object." + ex);
            throw new ExceptionInInitializerError(ex);

    public static org.hibernate.SessionFactory getFactory() {
        if (factory == null) {

        return factory;


One very important line in this class is #12. It is very important that you add the entity to the configuration. Without this step, hibernate will not know Book is an entity.

Finally, let’s create a book and insert it:

import entity.Book;
import org.hibernate.Session;
import org.hibernate.SessionFactory;
import org.hibernate.Transaction;

public class Runner {
    public static void main(String[] args) {

        Book b = new Book();
        b.setAuthor("No name");
        b.setTitle("Some book");
        SessionFactory factory = SessionFactoryMaker.getFactory();

        try (Session session = factory.openSession()) {
            Transaction tx = session.beginTransaction();
        } catch (Exception ex) {

Running this would create a record in the database:

You can find the full repo here

Posted on Leave a comment

Setup OpenProject With Docker & Nginx(with SSL)

So I recently need to manage some internal projects and don’t want to use a subscription from sites like Jira. After considering some open source options, I chose OpenProject since it’s quite simple to use (unlike redmine).

Setting up the site is quite simple, especially with docker. Let’s get started.

Configure a domain for the application

The first thing I did was to set up a domain to host the application. While it is possible to house it on this domain ( with a port, it doesn’t look pretty, though. All I need to do is to create a record on my nginx server and getting a SSL certificate with let’s encrypt.

It took around 5 minutes for the whole process. If you need tutorial on that topic, here is a good one:

Start the application using docker compose

The guys at OpenProject have done a nice job creating docker compose file that you can run right away. You can get the file here:

I wouldn’t change much rather that setting application port to something other than 8080 and bind it only to since I don’t want the application to be accessible outside through that port.

Here is my setting, for example:

You may also want to change the password of the database.

Configure nginx to forward requests to app

So you should have SSL cert and domain/subdomain setup right now. For me, the domain is and here is the configuration in nginx.

server {
    location / {
        proxy_pass_request_headers on;
        proxy_ssl_verify off;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-Proto https;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-for $remote_addr;
        proxy_hide_header X-Frame-Options;

    listen 443 ssl; # managed by Certbot
    # other details, filled by Certbot


Nothing fancy, but line #8 helps remove protocol mismatch notifications when you are in the app.

Update settings in the app

Finally, let’s update some settings that the app populated by default

It’s only necessary to update the hostname and protocol to https as depicted in the picture.

Now you are ready to start managing some cool projects.