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.

CulturarteWeb is a Jakarta EE web application that brings together two types of users: Proponentes (event promoters) who publish cultural event proposals, and Colaboradores (funders) who back those proposals in exchange for returns like free tickets or a share of the profits. The platform covers the full lifecycle — from proposal submission through collaboration, payment, and certificate generation.

Quick Start

Get CulturarteWeb running locally or with Docker in a few steps

Architecture

Understand the three-tier architecture: web layer, SOAP services, and database

Deployment

Deploy with Docker Compose or manually to a Tomcat server

Servlet Reference

Browse all HTTP endpoints: authentication, proposals, collaborations, and more

What You Can Do

Proposals

Create and manage cultural event proposals with images, categories, and funding targets

Collaborations

Back proposals and choose your return: free entry or profit share

Trello Integration

Export a Proponente’s proposals and collaborator data to a Trello board automatically

User Profiles

Follow other users, view rankings, and manage your account

Database Schema

Explore the MySQL schema: Propuesta, Colaboracion, Usuario, and more

Configuration

Configure SOAP/REST service hosts, API keys, and image paths via config.properties

Get Running in 3 Steps

1

Clone and configure

Copy config.properties to ~/.Culturarte/config.properties and set your web service hosts and API credentials.
2

Start with Docker Compose

Run docker-compose up --build to spin up both the Tomcat web application and the MySQL database in containers.
3

Open the app

Navigate to http://localhost:8080 — the Buscador (proposal search) is your landing page. Register as a Proponente or Colaborador to begin.
CulturarteWeb depends on an external business-logic service (ControllerWS via SOAP) and an optional REST service for Proponente profiles. Both must be running before the web application starts. See the Architecture page for the full picture.

Build docs developers (and LLMs) love