solopcloud/adempiere-backend repository overview

⁠Quick reference

• Mantained by: SOLOP⁠
• Where to get help: Gitter community ADempiere⁠, Git Project Adempiere-Backend⁠

⁠Supported tags and respective Dockerfile links

• alpine, latest ⁠

⁠What is ADempiere?

The ADempiere project was created in September 2006 after a long running disagreement between ComPiere Inc.⁠, the developers of Compiere™, and the community that formed around that project. The community believed Compiere Inc. placed too much emphasis on the open source lock-in/commercial nature of the project, rather than the community sharing/enriching nature of the project, and after an impassioned discussion decided to split from Compiere™ giving birth to the ADempiere project.

⁠What is ADempiere - Backend?

This is an docker image for publish Application Dictionary of ADempiere over gRPC service

⁠How to use this image

adempiere-backend requires access to a PostgreSQL database to store information. We'll use the adempiere-postgres Docker Image for the database requirements.

⁠Run the application using Docker Compose

The main folder of this repository contains a functional docker-compose.yml file. Run the application using it as shown below:

$ curl -sSL https://raw.githubusercontent.com/solop-develop/backend/experimental/build-docker/docker-compose.yml > docker-compose.yml
$ docker-compose up -d

⁠Using stack deploy or docker-compose

⁠Download a stack file

$ curl -sSL https://raw.githubusercontent.com/solop-develop/backend/experimental/build-docker/stack.yml > stack.yml

⁠For run use:

$ docker stack deploy -c stack.yml adempiere-backend

⁠Or:

$ docker-compose -f stack.yml up

Wait for it to initialize completely, and check swarm-ip:50059, localhost:50059, or host-ip:50059 (as appropriate).

⁠Using the Docker Command Line

If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:

⁠Step 1: Create a network

$ docker network create adempiere-network

⁠Step 2: Create a PostgreSQL container

$ docker run --name adempiere-database \ 
-p 5432:5432 \
-e POSTGRES_PASSWORD=mysecretpassword \ 
-e DB_NAME=adempiere \
-e ADEMPIERE_PASSWORD=adempiere \
--network adempiere-network
-d solopcloud/adempiere-postgres 

⁠Start an adempiere-base instance

docker run --name adempiere-application \  
-p 50059:50059 
-e DB_HOST=adempiere-database \
-e  DB_NAME=adempiere \
-e DB_PASSWORD=adempiere \
-e ADEMPIERE_APPS_TYPE=tomcat \ 
--network adempiere-network
-d solopcloud/adempiere-backend

Access your application at your-ip:50059

⁠Configuration

⁠Initializing a new instance

When the container is executed for the first time, it will execute the file start.sh

⁠Environment variables

• DB_TYPE: Database Type (Supported Oracle, PostgreSQL and MariaDB). Default PostgreSQL
• DB_HOST: Hostname for PostgreSQL server. Default: localhost
• DB_PORT: Port used by PostgreSQL server. Default: 5432
• DB_NAME: Database name that Adempiere-Backend will use to connect with the database. Default: adempiere
• DB_USER: Database user that Adempiere-Backend will use to connect with the database. Default: adempiere
• DB_PASSWORD: Database password that Adempiere-Backend will use to connect with the database. Default: adempiere
• ADEMPIERE_APPS_TYPE: Application Type for Database Management Connection. Default: wildfly
• SERVER_PORT: Port to access Adempiere-Backend from outside of the container. Default: 50059
• SERVICES_ENABLED: Services enabled. Default: access; business; core; dashboarding; dictionary; enrollment; log; ui; workflow; store; pos;
• SERVER_LOG_LEVEL: Log Level. Default: WARNING