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.

All runtime settings for CulturarteWeb live in a single properties file at ~/.Culturarte/config.properties. The Config.config singleton reads this file once when the application starts. If the file or its parent directory does not exist, they are created automatically the first time the application runs — the bundled default config.properties (from src/main/resources/) is copied into place so the application can start immediately with sensible defaults.
Config.config is a singleton loaded once at JVM startup. Restart Tomcat after making any changes to config.properties — live-editing the file while the application is running has no effect until the next startup.

​
Full configuration reference

KeyDefaultDescription
WEB_SERVICES_HOSTlocalhostHostname or IP address of the SOAP ControllerWS service
WEB_SERVICES_PORT9125Port on which the SOAP ControllerWS service is listening
SERVICE/controllerWSPath segment of the SOAP service endpoint
WEB_SERVICES_HOSTRlocalhostHostname or IP address of the REST proponentes service
WEB_SERVICES_PORTR9126Port on which the REST proponentes service is listening
SERVICER/proponentesBase path of the REST endpoint
WEB_HOSTlocalhostTarget host used by DeployServidorWeb.sh — set to an IP for remote deployment
USER_HOST_WEB(empty)SSH username for remote deployment via the deploy script
RUTA_IMGIMGRelative path (from the web root or mount point) where event images are stored
API_TOKEN(empty)Trello API token for board integration
API_KEY(empty)Trello API key for board integration

​
SOAP endpoint construction

The application constructs the full SOAP WSDL URL from three keys: 
http://{WEB_SERVICES_HOST}:{WEB_SERVICES_PORT}{SERVICE}?wsdl
With the default values this resolves to: 
http://localhost:9125/controllerWS?wsdl
This URL is also used during the Maven build by the jaxws-maven-plugin to generate Java client stubs from the WSDL (wsimport). The WEB_SERVICES_HOST and WEB_SERVICES_PORT values in config.properties are therefore read at both build time (by the properties-maven-plugin) and at runtime (by the Config.config singleton).

​
REST endpoint construction

The REST client constructs per-proponent URLs using: 
http://{WEB_SERVICES_HOSTR}:{WEB_SERVICES_PORTR}{SERVICER}/{nick}
With defaults, a lookup for nick jdoe becomes: 
http://localhost:9126/proponentes/jdoe

​
Trello credentials

API_KEY and API_TOKEN are required for any feature that reads from or writes to Trello boards. To obtain them:
  1. Log in to trello.com with the account that owns (or has access to) the target board.
  2. Navigate to the Power-Ups Admin portal.
  3. Create a new Power-Up (or use an existing one) and copy the API Key from the dashboard.
  4. Generate a Token by following the token authorization link shown on the same page and granting the requested permissions.
  5. Paste both values into config.properties:
API_KEY=your_api_key_here
API_TOKEN=your_api_token_here

​
Sample config.properties

A complete sample file with all available keys and their defaults: 
# 1. WEB SERVICE (Servidor soap)
WEB_SERVICES_HOST=localhost
WEB_SERVICES_PORT=9125
SERVICE=/controllerWS


# 2. WEB SERVICE (Servidor rest)
WEB_SERVICES_HOSTR=localhost
WEB_SERVICES_PORTR=9126
SERVICER=/proponentes


# Se Usa en Script si es local no es nesesario user
# Host para el servidor web
WEB_HOST=localhost

# Usuario del pc (para el host web en despliegue remoto)
USER_HOST_WEB=

# 3. Obtener IMG
RUTA_IMG="IMG"

# 4. Clave api Trello
API_TOKEN=
API_KEY=

​
How the singleton works

The Config.config class (src/main/java/Config/config.java) follows a simple eager-initialization singleton pattern:
  • The single instance is created when the class is first loaded.
  • The constructor calls verificarfile(), which:
    1. Creates ~/.Culturarte/ if the directory does not exist.
    2. Copies the bundled default config.properties from the classpath if no file is found at ~/.Culturarte/config.properties.
    3. Loads the file into a java.util.Properties object.
  • All callers retrieve values via Config.config.getInstance().getProps("KEY").
Because the properties object is populated only once during class initialization, any edits to config.properties after Tomcat has started are not picked up until the JVM restarts.

Build docs developers (and LLMs) love

Get started for freeTalk to us