Added the a Engineering Release stage and Company Release stage to travis.yml and added any required credentials to Travis.
Each release stage is triggered by a specific commit message, as listed in the "stages" section of travis.yml.
Provided a commit message to skip test stages if required, to speed up release process.
Global variables have been added to set the release version, development version and the community release version for the release stages.
* Bump cmis from 1.5 to 1.6 (#397)
* Bump javax.json from 1.0.4 to 1.1.4 (#399)
* Update travis config with develop branch
* Bump fabric8-maven-plugin from 4.2.0 to 4.3.1 (#368)
* Bump alfresco-messaging-repo from 1.2.13 to 1.2.15 (#312)
* Bump httpcore from 4.4.11 to 4.4.12 (#298)
* Bump json-path from 2.3.0 to 2.4.0 (#403)
* Bump joda-time from 2.10.3 to 2.10.5 (#371)
* Bump alfresco-data-model from 8.50.2 to 8.54 (#396)
* Bump dependency.cxf.version from 3.3.2 to 3.3.4 (#374)
* Bump dataprep from 2.2 to 2.3 (#402)
* Bump dependency.jackson.version from 2.9.9 to 2.10.1 (#392)
* Bump bcprov-jdk15on from 1.62 to 1.64 (#355)
* Bump alfresco-repository from 7.134 to 8.21 (#394)
* Add retries to cmis rendition test
* Bump alfresco-remote-api from 7.107 to 8.27 (#395)
* Bump quartz from 2.3.1 to 2.3.2 (#370)
* Bump httpclient from 4.5.9 to 4.5.10 (#304)
* Bump alfresco-data-model from 8.54 to 8.55 (#405)
* Bump httpclient-cache from 4.5.9 to 4.5.10 (#303)
* Bump postgresql from 42.2.6 to 42.2.8 (#313)
* Bump groovy from 2.5.5 to 2.5.8 (#401)
* Bump bcmail-jdk15on from 1.62 to 1.64 (#356)
* Bump dependency.javax.mail.version from 1.5.1 to 1.6.2 (#398)
* Additional fixed to CMIS Rendition test
* Mark integration test with a bug
* Mark REST API test with a bug
* Bump dependency.alfresco-spring-webscripts.version from 7.8 to 7.10 (#354)
* Bump alfresco-remote-api from 8.27 to 8.28 (#406)
* Bump alfresco-repository from 8.21 to 8.22 (#407)
* Bump alfresco-repository from 8.22 to 8.24 (#408)
* Mark a test in NodeLockTests with a bug
* Bump alfresco-repository from 8.24 to 8.25 (#410)
* Bump alfresco-core from 7.22 to 7.23 (#412)
* Bump alfresco-data-model from 8.55 to 8.57 (#413)
* Bump alfresco-repository from 8.25 to 8.27 (#414)
* Bump dependency.alfresco-spring-webscripts.version from 7.10 to 7.11 (#418)
* Bump webdav from 1.0 to 1.1 (#419)
* Bump alfresco-repository from 8.27 to 8.28 (#423)
* Bump ftp from 1.0 to 1.1 (#422)
* Exclude spring-jcl from spring-orm & spring-core to guard classpath collission with commons-logging module (#417)
* Bump alfresco-repository from 8.28 to 8.31 (#428)
* Bump ftp from 1.1 to 1.2 (#430)
* Bump alfresco-remote-api from 8.28 to 8.37 (#426)
* Bump webdav from 1.1 to 1.2 (#431)
* Bump alfresco-data-model from 8.57 to 8.59 (#437)
* Bump alfresco-remote-api from 8.37 to 8.40 (#438)
* Remove demo tests
* Bump alfresco-remote-api from 8.40 to 8.44 (#443)
* Bump alfresco-data-model from 8.59 to 8.60 (#445)
* Bump utility from 3.0.14 to 3.0.16 (#444)
* Bump ftp from 1.2 to 1.3 (#447)
* Bump alfresco-remote-api from 8.44 to 8.45 (#451)
* Bump webdav from 1.2 to 1.3 (#449)
* Bump alfresco-remote-api from 8.45 to 8.46 (#452)
* REPO-4751: Upgrade to Spring 5.2
* Bump alfresco-repository from 8.38 to 8.39 (#453)
* Bump postgresql from 42.2.8 to 42.2.9 (#454)
* Bump alfresco-repository from 8.39 to 8.40 (#456)
* Bump alfresco-remote-api from 8.46 to 8.47 (#457)
* Bump alfresco-remote-api from 8.47 to 8.48 (#459)
* upgrade mockito library (#455)
* Bump alfresco-remote-api from 8.48 to 8.50 (#460)
* Bump alfresco-data-model from 8.60 to 8.61 (#462)
* Bump mockito-core from 3.0.0 to 3.2.0 (#464)
* Bump alfresco-repository from 8.40 to 8.41 (#461)
* Bump alfresco-remote-api to 8.51 and alfresco-repository to 8.42
* [maven-release-plugin] prepare release acs-community-packaging-6.3.0-A2
* [maven-release-plugin] prepare for next development iteration
* REPO-4785 Performance improvements to REST API TAS tests (#466)
* Mark test with a bug
* Mark test with a bug
* Mark test with a bug
* Mark test with a bug
* Bump restapi from 1.15 to 1.23 (#463)
* Bump alfresco-data-model from 8.61 to 8.66 (#467)
* Revert "Mark test with a bug"
This reverts commit 7a80d9c539.
* Revert "Mark test with a bug"
This reverts commit 5922f4a0fe.
* Revert "Mark test with a bug"
This reverts commit 5b6cf02b64.
* Revert "Mark test with a bug"
This reverts commit 1b874fbccb.
* REPO-4785 Remove reduced timeout config in tests
Previous iteration of improving test performance introduced a few intermittent failures into tests. This PR removes those changes, but leaves the split in the REST API tests.
* Bump alfresco-remote-api from 8.51 to 8.52 (#469)
* Bump alfresco-data-model from 8.66 to 8.67 (#471)
* Bump alfresco-core from 8.2 to 8.6 (#468)
* Bump alfresco-repository from 8.42 to 8.43 (#470)
* Bump dependencies (#472)
Bump repository to 8.44
Bump data-model to 8.68
Bump remote-api to 8.55
* Bump mockito-core from 3.2.0 to 3.2.4 (#473)
* Bump alfresco-repository from 8.44 to 8.46 (#474)
* Bump utility from 3.0.16 to 3.0.17 (#475)
* Bump restapi from 1.24 to 1.25 (#476)
* Bump alfresco-remote-api from 8.55 to 8.57 (#477)
* Bump jackson-databind 2.9.10 -> 2.10.1 (#479)
* Bump alfresco-remote-api from 8.57 to 8.59 (#481)
* Bump restapi from 1.25 to 1.26 (#483)
* Bump ftp from 1.3 to 1.4 (#484)
* Bump alfresco-core from 8.6 to 8.7 (#487)
* Bump alfresco-repository from 8.46 to 8.48 (#488)
* Bump webdav from 1.3 to 1.4 (#485)
* Bump alfresco-data-model from 8.68 to 8.70 (#489)
* Pickup upstream projects
* REPO-4739 update dependencies of tas framework (#776) (#494)
* Update all tas packages, now with Dependabot enabled
dependency.tas-utility.version>3.0.17
dependency.tas-restapi.version>1.26
dependency.tas-cmis.version>1.12
dependency.tas-email.version>1.7
dependency.tas-webdav.version>1.4
dependency.tas-ftp.version>1.4
Cherry-picked from acs-packaging PR #776
* Bump alfresco-remote-api from 8.62 to 8.63 (#496)
* Bump alfresco-core from 8.9 to 8.10 (#497)
* Bump alfresco-remote-api from 8.63 to 8.64 (#499)
* Bump alfresco-remote-api from 8.64 to 8.65 (#500)
* Bump alfresco-remote-api from 8.65 to 8.66 (#502)
* Bump alfresco-data-model from 8.72 to 8.73 (#503)
* Bump alfresco-remote-api from 8.66 to 8.67 (#505)
* Bump alfresco-remote-api from 8.67 to 8.68 (#506)
* Bump junit from 4.12 to 4.13 (#507)
* Bump alfresco-remote-api from 8.68 to 8.69 (#512)
* Bump commons-codec from 1.13 to 1.14 (#511)
* Bump alfresco-data-model from 8.73 to 8.74 (#513)
* Bump alfresco-core from 8.10 to 8.11 (#514)
* Bump dependency.jackson.version from 2.10.1 to 2.10.2 (#518)
* Bump alfresco-remote-api from 8.69 to 8.73 (#519)
* Bump webdav from 1.4 to 1.5 (#520)
* Bump alfresco-data-model from 8.74 to 8.75 (#521)
* Bump api-explorer from 6.2.0 to 6.2.1 (#524)
* Bump alfresco-core from 8.11 to 8.12 (#523)
* REPO-4917 : Update upstream projects (#517)
* REPO-4917 : Update upsteam projects
Bump remote-api to 8.73
Bump repository to 8.61
Bump data-model to 8.75
Bump core to 8.12
Bump api-explorer to 6.2.1
* Remove unsoported transformation PDF -> PDF
LocalPassThroughTransform was added and supports same source/target mimetype
Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
Co-authored-by: Alex Mukha <killerboot@users.noreply.github.com>
Co-authored-by: Abdul Mohammed <abdul.mohammed@alfresco.com>
Co-authored-by: Cristian Turlica <cristian.turlica@ness.com>
Co-authored-by: NITHIN NAMBIAR <nithinnambiar@yahoo.co.in>
Co-authored-by: alandavis <alan.davis@alfresco.com>
Co-authored-by: alfresco-build <alfresco-build@users.noreply.github.com>
Co-authored-by: David Edwards <david.edwards@alfresco.com>
* REPO-4917 : Update upsteam projects
Bump remote-api to 8.73
Bump repository to 8.61
Bump data-model to 8.75
Bump core to 8.12
Bump api-explorer to 6.2.1
* Remove unsoported transformation PDF -> PDF
LocalPassThroughTransform was added and supports same source/target mimetype
* Update all tas packages, now with Dependabot enabled
dependency.tas-utility.version>3.0.17
dependency.tas-restapi.version>1.26
dependency.tas-cmis.version>1.12
dependency.tas-email.version>1.7
dependency.tas-webdav.version>1.4
dependency.tas-ftp.version>1.4
Cherry-picked from acs-packaging PR #776
Previous iteration of improving test performance introduced a few intermittent failures into tests. This PR removes those changes, but leaves the split in the REST API tests.
* REPO-4747: Update dependencies
Bump alfresco-repository to 7.107.1 and alfresco-remote-api to 7.134.1
Update CHANGELOG.MD with 201911 GA release.
Bump SOLR6 to 1.4.0 in test/docker-compose
Update SOLR env for test/docker-compose
* REPO-4631 Update jackson-databind version to 2.9.9.3
* REPO-4631 Update jackson-databind version to 2.9.9.3
* changed also remote-api and repository versions
Addition of Local Transforms which will ultimately replace the Legacy transformers. Local transforms use T-Engines running outside of the JVM. They are automatically created by adding either an Alfresco global property or System property. There is no spring configuration or Java code needed, reducing the need for an AMP when creating a custom transform.
Mainly bringing in the T-Engines.
REPO-4319 Local Transformers
REPO-4454 Test addition and removal of T-Engines
REPO-4326 Local Transformer strict mime type check
REPO-4333 Configure Custom local transformers
REPO-4331 Remaining core transformers
REPO-4336 Client side of Transform Server Discovery API
REPO-4450 Get T-Router /transform/config working
REPO-4451 Get repo,api,ent-repo,ent-api,pack,com-pack green
Bumps `dependency.cxf.version` from 3.3.1 to 3.3.2.
Updates `cxf-rt-frontend-jaxws` from 3.3.1 to 3.3.2
Updates `cxf-rt-frontend-jaxrs` from 3.3.1 to 3.3.2
Updates `cxf-rt-rs-client` from 3.3.1 to 3.3.2
Updates `cxf-rt-transports-http` from 3.3.1 to 3.3.2
Updates `cxf-rt-ws-policy` from 3.3.1 to 3.3.2
Signed-off-by: dependabot[bot] <support@dependabot.com>
* REPO-4400_Moving keystore folder contents
In removing the ssl.keystore and ssl.truststore the following files were found. It was discussed with Alex M that it would be more appropriate for these to be part of packaging.
* Update .gitignore
* REPO-4219 create CORS context listener
* REPO-4219 enable cors for test
* REPO-4219 add origin localhost 4200 for REST TAS test
* REPO-4219 Remove thetransactioncompany dependency
* Added Licenses directory to the root of docker image
* Updated artefactId correctly for community packaging
* Replaced maven-dependency-plugin with maven-resources-plugin to copy licenses from source code
* Replaced maven-dependency-plugin with maven-resources-plugin to copy licenses from source code
The workflow diagrams could not be generated because sun.font package classes require system fonts to be installed.
The current docker image requires additional package (fontconfig) to be added. It's version and the versions of the dependencies were pinned.
Revert "REPO-3160: Add email tests to ACS community build plan"
This change was not required as the tas email tests without jmx are passing on the origin docker compose. The build plan is updated and the email tests are passing.
REPO-3160: Add the email TAS tests to our builds
Add a test image in the community project and created a new maven module in order to not affect the running tas tests (integration tests where failing with the changes for email tests).
This test image has some port exposed in order to run the tas email tests.
* REPO-3539 : Integrate Api-Explorer
Add alfresco-api-explorer version property to pom.xml
Add alfresco-api-explorer dependency to docker-alfresco/pom.xml and unpack it using maven-dependency-plugin
API-Explorer Url is now generated in UrlUtil.
Update alfresco-repository version.
CSRF filter is now configured by these props:
csrf.filter.referer=
csrf.filter.referer.always=false
csrf.filter.origin=
csrf.filter.origin.always=false
Referer and origin here is a regexp and should look like:
http://mydomain:80/*.
* REPO-3457 : Remove /docker-compose
Add test.env to /docker-alfresco/test/
Add share image, repository is on debug by default, remove references to docker.io, add REPOSITORY variable for repository images on quay.io.
Quartz uses c3p0 jdbc pool for it's distributed job storage since version 2.x
This commit will exclude c3p0 lib as distributed job storage is not used.
* REPO-3378: Integrate zip module into full-distribution module
Rena,e full-distribution module to distribution.
Remove zip module
Remove zip module from the superPom
# Must be in the format <alfresco-version>-<additional_versioning> ie. 6.3.0-repo-xxxx-x or 6.3.0-Ax
- RELEASE_VERSION=7.0.0-TEST4
- DEVELOPMENT_VERSION=7.0.0-TEST5-SNAPSHOT
stages:
- name:test
if:commit_message !~ /\[skip tests\]/
- name:docker_latest
if:fork = false AND type != pull_request AND branch = master
- name:release
if:commit_message ~= /\[release\]/ AND fork = false AND type != pull_request AND (branch =~ ^(master|develop)$ OR branch =~ /release\/.*/ OR branch = feature/REPO-5111_repo_build)
- name:publish
if:commit_message ~= /\[publish\]/ AND fork = false AND type != pull_request AND (branch =~ ^(master|develop)$ OR branch =~ /release\/.*/)
<h1> Release Notes - Alfresco - Version Community Edition 201911 GA
</h1>
<h2> Bug
</h2>
<ul>
<li>[<a href='https://issues.alfresco.com/jira/browse/MNT-20436'>MNT-20436</a>] - “POST /nodes/{nodeId}/children” RestAPI does not create a node without having a mandatory value object, but it outputs the 201 successful response.
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/MNT-20714'>MNT-20714</a>] - [HotFix] /nodes/{nodeId}/content REST API fails for content created by a deleted user
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/MNT-20770'>MNT-20770</a>] - Share non responsive during direct download from S3 if content store selector is also configured
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/MNT-20863'>MNT-20863</a>] - Changing cm:name with REST API /nodes/{nodeId} does not update Primary Path
</li>
</ul>
<h1> Release Notes - Alfresco - Version Community Edition 201910 EA
</h1>
<h2>
New Features
</h2>
<ul>
<li>
<h4>Custom Transforms and Renditions</h4>
<p>Alfresco Content Services (ACS) provides a number of content
transforms, but also allows custom transforms to be added.
<p>It is now possible to create custom transforms that run in
separate processes known as T-Engines (short for Transformer
Engines). The same engines may be used in Community and
Enterprise Editions. They may be directly connected to the ACS
repository as Local Transforms, but in the Enterprise edition there
is the option to include them as part of the Transform Service
which provides more balanced throughput and better administration
capabilities.
<p>For more information see <a href='https://github.com/Alfresco/acs-packaging/blob/master/docs/custom-transforms-and-renditions.md'>Custom Transforms and Renditions</a>
</li>
<li>
<h4>Open-source Transformation Engines</h4>
<p>The core T-Engine images can now be used in Community
Edition.</p>
<p>T-Engines code has been Open-Sourced and is available on Github:</p>
<h4>Removal of external executables from docker image</h4>
<p>With the introduction of the new Local Transform Service
in Alfresco Community Edition, the capability of executing
remote transformations on T-Engines was enabled. Because of
this, the external executables (Alfresco-Pdf-renderer, Libreoffice
and Imagemagick) have been removed from the docker container to
facilitate the usage of out-of-process transformations.
</p>
</li>
</ul>
<h2> Bug
</h2>
<ul>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22013'>ALF-22013</a>] - Docker Image for Base Tomcat locale is POSIX
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22060'>ALF-22060</a>] - Reader on the backing store is obtained twice in CachingContentStore
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22056'>ALF-22056</a>] - onCopyCompleteBehaviour not called in order of copy-action
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22073'>ALF-22073</a>] - MailActionExecutor doesn't consider email bodies with a HTML doctype as HTML
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-21988'>ALF-21988</a>] - Tab order for number ranges not ok
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22097'>ALF-22097</a>] - T Engine - add source nodeId parameter
</li>
</ul>
<h2> Improvement
</h2>
<ul>
<li>[<a href='https://issues.alfresco.com/jira/browse/REPO-4318'>REPO-4318</a>] - [COMPLETE] Extraction of transformers and metadata extractors
</li>
</ul>
<h2>
<h1> Release Notes - Alfresco - Version Community Edition 201901 GA
<p>ACS is now runnable with OpenJDK 11.0.1. It still remains compatible with JDK 1.8.</p>
</li>
</ul>
<h2> Bug
</h2>
<ul>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22049'>ALF-22049</a>] - Alfresco does not start
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22041'>ALF-22041</a>] - EKS deployment - SOLR_ALFRESCO_HOST set to wrong host name
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22031'>ALF-22031</a>] - REST API calls silently rollback after the returning a success status
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-21963'>ALF-21963</a>] - Workflow - backslash in nodeRef properties url.
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-21803'>ALF-21803</a>] - Unable to add users to sites whose 'short name' is a substring of 'site'
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-21664'>ALF-21664</a>] - Exception on workflow image by REST API
<li>[<a href='https://issues.alfresco.com/jira/browse/REPO-7'>REPO-7</a>] - Embed ActiveMQ in the Platform
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/REPO-1957'>REPO-1957</a>] - Transformations Improvement Plan
</li>
</ul>
<h2>
Deprecations
</h2>
<ul>
<li>
TransformService and RenditionService: All Java APIs related to TransformService and RenditionService have been deprecated; the ability to perform arbitrary transformations will be phased out as the new DBP Transform Service takes effect. Renditions can be triggered using the existing repository REST API but will be processed asynchronously using the new services.<br/>
</li>
</ul>
<h2>
Known issues
</h2>
<ul>
<li>
Due to the changes to the RenditionService the Media Management AMP is not supported yet.<br/>
</li>
</ul>
<h2>
<h1> Release Notes - Alfresco - Version Community Edition 201810 EA
</h1>
<h2> Bug
</h2>
<ul>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-21783'>ALF-21783</a>] - ScriptAuthorityService: No way to get more than 100 results with some methods
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-21917'>ALF-21917</a>] - Document list edit metadata incorrect url escaping
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22001'>ALF-22001</a>] - Faceted search does not work in Japanese
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22030'>ALF-22030</a>] - ADF UI freezes noticeably on a periodic basis during KeyCloak auth requests
<li>[<a href='https://issues.alfresco.com/jira/browse/REPO-3703'>REPO-3703</a>] - AWS Services: Native Services of ACS
</li>
</ul>
<h2>
<h1> Release Notes - Alfresco - Version Community Edition 201808 EA
</h1>
<h2> Bug
</h2>
<ul>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-21992'>ALF-21992</a>] - BehaviourFilterImpl.isEnabled(NodeRef, QName) is checking wrong QName in case of subClass
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22006'>ALF-22006</a>] - VersionServicePolicies cannot be disabled on a specific node
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22007'>ALF-22007</a>] - TransactionListeners are executed in unpredictable order
</li>
</ul>
<h2> Improvement
</h2>
<ul>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22011'>ALF-22011</a>] - Upgrade to XMLBeans 3.0.0
</li>
</ul>
<h1> Release Notes - Alfresco - Version Community Edition 201806 GA
</h1>
<h2> Bug
</h2>
<ul>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22000'>ALF-22000</a>] - Docker: HTML link 693ce565f4c4:8080/share but name
</li>
<li>[<a href='https://issues.alfresco.com/jira/browse/ALF-22008'>ALF-22008</a>] - It is not possible to upload a document without versions using CMIS
@@ -7,89 +7,31 @@ The SNAPSHOT version of the artifacts is **never** published.
### Contributing guide
Please use [this guide](CONTRIBUTING.md) to make a contribution to the project.
This project contains the code for packaging the entire Alfresco Content Services product Community edition.
This produces the docker images for alfresco-content-repository-community and the distribution zip for the entire Alfresco Content Services Community product
# General
## General
### Build:
* ```mvn clean install``` in the root of the project will build everything.
## Docker-compose & Kubernetes
Build and start Alfresco Content Services Community using docker-compose or Kubernetes, containing:
1. Alfresco Repository for community, with:
1.1. Alfresco Share Services amp
1.2. Alfresco AOS amp
1.3. Alfresco vti-bin war - that helps with AOS integration
1.4. Alfresco Google Docs Repo amp
2. Alfresco Share, with:
2.1 Alfresco Google Docks Share amp
3. A Postgres DB
4. Alfresco Solr6
## Docker Alfresco
On official releases, the image is published: https://hub.docker.com/r/alfresco/alfresco-content-repository-community/tags/
### Docker Compose Instructions:
#### Prerequisite:
* Docker installed locally
* Access to docker-internal.alfresco.com and quay.io repositories - Platform Services team is working on getting the images in [Docker Hub](https://hub.docker.com/u/alfresco/) registry.
#### Steps
1. Go to **docker-compose** folder
2. Run ```docker-compose up```
3. Check that everything starts up with the browser: http://localhost:8082/alfresco and http://localhost:8080/share and http://localhost:8083/solr/
#### Notes:
* Make sure the local machine has the ports (5432, 8080, 8082, 8083) set up in the docker-compose.yml file free.
* The images used in the docker-compose.yml are images that are build in the 'docker-alfresco' and 'docker-share' subfolders of the project - see the relevant sections below
* If you don't have access to the docker-internal.alfresco.com and quay.io images, or if you want custom data in your docker images, you can use the 'docker-alfresco' and 'docker-share' folders to customize and build your customized docker images that are used in the docker-compose project. Just make sure you use proper tags when you create the images and update the docker-compose.yml with these proper tags that you created.
### Kubernetes Instructions:
#### Prerequisite:
* Deploy the infrastructure chart as specified in https://github.com/Alfresco/alfresco-infrastructure-deployment
* Access to docker-internal.alfresco.com and quay.io repositories - Platform Services team is working on getting the images in [Docker Hub](https://hub.docker.com/u/alfresco/) registry.
* A kubernetes secret (quay-registry-secret) with the above mentioned credentials created in your cluster.
**Note!** You do not need to pull this repo in order to deploy Alfresco Content Services in Kubernetes
#### Steps
1. Run ```helm repo add alfresco-incubator http://kubernetes-charts.alfresco.com/incubator``` to add the Alfresco Kubernetes repository to helm.
3. After deploying the helm chart you will get information for obtaining the URL for repository, share and solr.
#### Notes:
* The images used in the alfresco-content-services/values.yml are images that are built in the 'docker-alfresco' and 'docker-share' subfolders of the project - see the relevant sections below.
* If you don't have access to the docker-internal.alfresco.com and quay.io images, or if you want custom data in your docker images, you can use the 'docker-alfresco' and 'docker-share' folders to customize and build your customized docker images that are used in the docker-compose project. Just make sure you build them in the minikube docker environment and update the alfresco-content-services/values.yml with the tags that you created.
* You can also change those values when deploying the helm chart by running ```helm install alfresco-incubator/alfresco-content-services --set repository.image.tag="yourTag" --set share.image.tag="yourTag"```.
* Hint: Run ```eval $(minikube docker-env)``` to switch to your minikube docker environment on osx.
## Docker images
These images are used to build the images used by the docker-compose.yml project to bring up an ACS Community, similar to what the installer did/does.
### Docker Alfresco
1. Go to docker-alfreco folder
For testing locally:
1. Go to docker-alfresco folder
2. Run *mvn clean install* if you have not done so
3. Build the docker image: ```docker build . --tag my-acs-repo:6.0.test```
4. Check that the image has been created locally with your desired name/tag: ```docker images```
### Docker Share
1. Go to docker-share folder
2. Run *mvn clean install* if you have not done so
3. Build the docker image: ```docker build . --tag my-share:5.2.test```
3. Build the docker image: ```docker build . --tag acr-community:6.0.tag```
4. Check that the image has been created locally with your desired name/tag: ```docker images```
### Docker-compose & Kubernetes
Use the deployment project if you want the sample docker-compose or helm: https://github.com/Alfresco/acs-community-deployment
## Distribution zip
In this folder the distribution zip is build. It contains all the war files, libraries, certificates and settings files you need to deploy Alfresco Content Services Community on the supported application servers.
In this folder the distribution zip is build. It contains all the war files, libraries, certificates and settings files you need to deploy alfresco on the supported application servers.
## How to
* [Create a custom Docker image](https://github.com/Alfresco/acs-packaging/blob/master/docs/create-custom-image.md)
* [Creating customized Docker images using an existing Docker image](https://github.com/Alfresco/acs-packaging/blob/master/docs/create-custom-image-using-existing-docker-image.md)
* [Verifying that AMPs have been applied](https://github.com/Alfresco/acs-packaging/blob/master/docs/verify-the-amp-has-been-applied.md)
* [Create and configure custom Transforms](https://github.com/Alfresco/acs-packaging/blob/master/docs/custom-transforms-and-renditions.md)
<store password> is the keystore password. The file ${dir.keystore}/ssl-keystore-passwords.properties contains passwords for the SSL keystore,
${dir.keystore}/ssl-truststore-passwords.properties contains passwords for the SSL truststore.
These instructions will create an RSA public/private key pair for the repository with a certificate that has been signed by the Alfresco Certificate Authority (CA).
It will also create a truststore for the repository containing the CA certificate; this will be used to authenticate connections to specific repository
URLs from Solr. It assumes the existence of the Alfresco CA key and certificate to sign the repository certificate; for security reasons these are not generally available.
You can either generate your own CA key and certificate (see instructions below) or use a recognised Certificate Authority such as Verisign. For Alfresco employees the key
and certificate are available in svn.
(i) Generate the repository public/private key pair in a keystore:
(vi) Convert the repository keystore to a pkcs12 keystore (for use in browsers such as Firefox). Give the pkcs12 key store the key store password 'alfresco'.
(vii) Copy the keystore and truststore to the repository keystore location defined by the property 'dir.keystore'.
(viii) Update the SSL properties i.e. properties starting with the prefixes 'alfresco.encryption.ssl.keystore' and 'alfresco.encryption.ssl.truststore'.
Instructions for Generating a Certificate Authority (CA) Key and Certificate
See https://wiki.alfresco.com/wiki/Data_Encryption and https://wiki.alfresco.com/wiki/Alfresco_And_SOLR.
keystore is the secret key keystore, containing the secret key used to encrypt and decrypt node properties.
ssl.keystore is the repository keystore, containing the repository private/public key pair and certificate.
ssl.truststore is the repository truststore, containing certificates that the repository trusts.
browser.p12 is a pkcs12 keystore generated from ssl.keystore that contains the repository private key and certificate for use in browsers such as Firefox.
The authoratitive ImageMagick license can be found at
The authoritative ImageMagick license can be found at
http://www.imagemagick.org/script/license.php and ImageMagick notices at
http://www.imagemagick.org/www/Notice.html.
Before we get to the text of the license lets just review what the license says in simple terms:
Before we get to the text of the license, lets just review what the license says in simple terms:
It allows you to:
* freely download and use ImageMagick software, in whole or in part, for personal, company internal, or commercial purposes;
* use ImageMagick software in packages or distributions that you create.
* use ImageMagick software in packages or distributions that you create;
* link against a library under a different license;
* link code under a different license against a library under this license;
* merge code into a work under a different license;
* extend patent grants to any code using code under this license;
*and extend patent protection.
It forbids you to:
@@ -27,39 +32,42 @@ It does not require you to:
A few other clarifications include:
* ImageMagick is freely available without charge;
* you may include ImageMagick on a CD-ROM as long as you comply with the terms of the license;
* you may include ImageMagick on any digital media as long as you comply with the terms of the license;
* you can give modified code away for free or sell it under the terms of the ImageMagick license or distribute the result under a different license, but you need to acknowledge the use of the ImageMagick software;
* the license is compatible with the GPL.
* the license is compatible with the GPL V3.
* when exporting the ImageMagick software, review its export classification.
Terms and Conditions for Use, Reproduction, and Distribution
The legally binding and authoritative terms and conditions for use, reproduction, and distribution of ImageMagick follow:
Copyright 1999-2005 ImageMagick Studio LLC, a non-profit organization dedicated to making software imaging solutions freely available.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication intentionally sent to the Licensor by its copyright holder or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
@@ -82,3 +90,21 @@ You may add Your own copyright statement to Your modifications and may provide a
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
How to Apply the License to your Work
To apply the ImageMagick License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information (don't include the brackets). The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the ImageMagick License (the "License"); you may not use
this file except in compliance with the License. You may obtain a copy
of the License at
https://www.imagemagick.org/script/license.php
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations
{{- range $key, $val := .Values.solr.environment }}
{{$key }}:{{$val | quote }}
{{- end }}
{{- end }}
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.