Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/17Franco/CulturarteWeb/llms.txt

Use this file to discover all available pages before exploring further.

This guide walks you through everything needed to get CulturarteWeb running on your local machine. You will clone the repository, create a config.properties file that tells the application where to find the external SOAP and REST services, and then bring the app up — either via Docker Compose (recommended) or by deploying the WAR manually to a local Tomcat instance.

​
Prerequisites

Before you begin, make sure the following are available on your machine:
  • Java 21 (required by both the Maven build and the Tomcat runtime)
  • Maven 3.x (for building the WAR artifact)
  • Docker and Docker Compose — required for the Docker path
  • Tomcat 10.1 — required for the manual path
  • The ControllerWS SOAP service running and reachable (see the warning below)
The ControllerWS SOAP service must be running and accessible at the host and port you configure in config.properties before starting the CulturarteWeb application. Without it, login, registration, proposal management, and all other business operations will fail immediately. Start ControllerWS first.

​
config.properties Template

Both deployment paths require a config.properties file placed at ~/.Culturarte/config.properties. If this file does not exist when the application starts, the config singleton will automatically copy the bundled default from the WAR’s classpath — but that default uses localhost addresses, which may not match your environment. Create the file manually to ensure the correct values are in place: 
# SOAP service (ControllerWS)
WEB_SERVICES_HOST=localhost
WEB_SERVICES_PORT=9125
SERVICE=/controllerWS

# REST service (Proponente profile data)
WEB_SERVICES_HOSTR=localhost
WEB_SERVICES_PORTR=9126
SERVICER=/proponentes

# Web host (used by deployment scripts; leave empty for local)
WEB_HOST=localhost
USER_HOST_WEB=

# Image directory path
RUTA_IMG="IMG"

# Trello API credentials (required for Trello board export)
API_TOKEN=
API_KEY=

​
Deployment

The Docker Compose setup builds the WAR, packages it into a tomcat:10.1-jdk21 container, and starts a mysql:8.0.17 database container alongside it. The database is pre-seeded from copia.sql and persisted in a named volume.
1

Clone the repository

git clone https://github.com/17Franco/CulturarteWeb.git
cd CulturarteWeb
2

Create config.properties

Create the configuration directory and file in your home folder. Replace the host/port values if your ControllerWS service is running on a different machine or port.
mkdir -p ~/.Culturarte
Then create ~/.Culturarte/config.properties with the template shown above. For a fully local setup the default values (localhost:9125 / localhost:9126) are sufficient.
3

Build the WAR and start all services

Docker Compose will call mvn clean install as part of the build context, package the WAR as Culturarte.war, and deploy it to Tomcat’s webapps/ROOT.war so the app is reachable at the root path.
docker-compose up --build
Docker will start two containers:
  • appCulturarteWeb — Tomcat 10.1 on port 8080
  • BaseDatosC — MySQL 8 on port 3307 (mapped from internal 3306)
4

Open the application

Once both containers are healthy, navigate to:
http://localhost:8080
You will be redirected to the BuscadorPropuestas welcome servlet automatically.

​
What’s Next

Docker Deployment Details

Understand the Dockerfile, compose services, volume mounts, and how the MySQL container is seeded.

Configuration Reference

Full reference for every key in config.properties, including Trello API credentials and image path setup.

Proposals

Learn how Proponentes create, extend, and cancel cultural event proposals.

Build docs developers (and LLMs) love

Get started for freeTalk to us