How redpill-linpro/alfresco-s3-adapter works
Project type and purpose
• This is a full-stack, All-In-One (AIO) Docker-based Alfresco environment with a custom S3 content store adapter.
• It orchestrates multiple services (Alfresco Content Service, Share, Search Service, PostgreSQL) plus the AWS S3 backend for binary storage.
File structure
• Top-level modules (Maven artifacts):
• alfresco-s3-adapter-platform: The ACS extension jar, contains S3ContentStore, reader/writer, Spring contexts.
• alfresco-s3-adapter-share: The Share UI extension jar (web fragments).
• alfresco-s3-adapter-platform-docker & alfresco-s3-adapter-share-docker: Dockerfile + config for custom ACS and Share images.
• alfresco-s3-adapter-testdeps: Additional AMP dependencies.
• integration-tests: IT suite that exercises the running system.
• docker/docker-compose.yml: Orchestrates the containers.
• run.sh / run.bat: High-level script to build modules, build Docker images, start/stop the environment, run ITs.
Extracting insights from the README
• The AIO project builds JAR modules (no wars), packages them into custom Docker images, then starts containers for:
• ACS (Alfresco Content Service)
• Share (Alfresco Share UI)
• ASS (Alfresco Search Service)
• PostgreSQL
• The adapter uses AWS Java SDK to read/write content to an S3 bucket.
• Integration tests run against the live Docker environment.
Main components
a. Developer workstation
– Git repo + run.sh script → triggers Maven build and docker-compose
b. Docker Host (or Kubernetes) running containers:
1. Alfresco Content Service (custom image)
• Contains the platform jar (S3ContentStore beans, context XMLs)
• Connects to Postgres for metadata
• Connects to AWS S3 for content
• Connects to ASS for indexing
2. Alfresco Share (custom image)
• Contains the Share extension jar (UI web fragments)
• Talks to ACS via REST APIs
3. Alfresco Search Service
• Indexes content & metadata via Solr cores
4. PostgreSQL
• Stores Alfresco node and properties data
c. External AWS S3
• The actual storage backend for binaries
d. Integration-tests module (runs from developer machine or CI)
• Uses TestContainers or direct TCP to test ACS + Share + S3 behavior
Relationships and data flows
• User → Share UI (HTTP) → Share container
• Share → ACS (HTTP/Alfresco public API)
• ACS → Postgres (JDBC) for metadata
• ACS → S3 (AWS SDK calls over HTTPS) for binaries
• ACS → ASS (REST/Solr) for indexing
• Integration tests → Docker network → endpoints of ACS & Share & S3-mock
Architectural patterns & technologies
• Micro-services in containers behind Docker Compose
• Modular JARs deployed via Docker images (no WARs)
• Spring bean configuration via XML (S3 contexts, module contexts)
• Assembly of AMPs via Maven assembly plugin (but packaging into jars)
• Use of AWS SDK 1.x, Alfresco SDK 3.0/4.0, Docker volumes for persistence
• Optional hot-reloading with JRebel in dev images