-
Notifications
You must be signed in to change notification settings - Fork 8
Building TAP from Sources
Wiki Home ▸ Building TAP from Sources
Before you start, make sure that you have the required [ tools ] (Development Environment Setup) installed. You should have completed previous step for infrastructure building (AWS or Openstack).
Instructions included in AWS and Openstack allow to create platform infrastructure with default application layer dedicated for 0.7 release. After edition apps sources or TAP configuration settings application layer on existing TAP environment should be redeployed. Platform parent is a tool, which builds sources and creates deployable artifacts from TAP applications sources. Having rebuilt artifacts they can be deployed using apployer tool. Apployer component is also responsible for TAP configuration settings, so it has to be used after configurations settings changes.
- Clone platform-parent repository.
- Set platform-parent version using command
git checkout v0.7
- Create a new directory where prepared artifacts will be stored:
mkdir <ARTIFACTS_OUTPUT_PATH>
- Enter
platform-parent/docker
directory. - Run following command to create docker image:
./build_tap.sh build
. - Run docker container by executing:
./build_tap.sh run PLATFORM_PARENT_PATH ARTIFACTS_OUTPUT_PATH --release-tag=v0.7
where:
PLATFORM_PARENT_PATH - path to cloned platform-parent repository
ARTIFACTS_OUTPUT_PATH - path to directory created in point 3
Artifacts should be created and ready to deploy.
At this stage apployer tool will be used:
-
Enter
<PLATFORM_PARENT_PATH>/apployer
directory. -
Follow setup instructions
-
Fill the fetcher_config.yml file with values corresponding to your TAP instance.
-
If needed change values in VARIABLES FOR MANUAL CHANGE section of templates/template_variables.yml.
-
Run apployer deploy command. Example:
apployer deploy -p CF_PASSWORD -o CF_ORG_NAME -s CF_SPACE_NAME PLATFORM_PARENT_ARTIFACTS_OUTPUT_PATH/apps/ https://cf-api.{{ CF_DOMAIN }}