--- title: Customizing Server Profiles description: When you deployed the full stack of product containers in Getting Started, you used the server profiles associated with each of our products. In the YAML files, you'll see entries like the following for each product instance: component: devops page_id: devops::how-to/profiles canonical_url: https://developer.pingidentity.com/devops/how-to/profiles.html section_ids: devops-before-you-begin: Before you begin devops-about-this-task: About this task devops-adding-or-changing-environment-variables: Adding or Changing Environment Variables devops-modifying-a-server-profile: Modifying a Server Profile devops-using-your-github-repository: Using Your Github Repository devops-using-local-directories: Using Local Directories --- # Customizing Server Profiles When you deployed the full stack of product containers in [Getting Started](../get-started/introduction.html), you used the server profiles associated with each of our products. In the YAML files, you'll see entries like the following for each product instance: ```yaml environment: - SERVER_PROFILE_URL=https://github.com/pingidentity/pingidentity-server-profiles.git - SERVER_PROFILE_PATH=baseline/pingaccess ``` Our [pingidentity-server-profiles](https://github.com/pingidentity/pingidentity-server-profiles) repository, indicated by the `SERVER_PROFILE_URL` environment variable, contains the server profiles we use for our DevOps deployment examples. The `SERVER_PROFILE_PATH` environment variable indicates the location of the product profile data to use. In the previous example, the PingAccess profile data is located in the `baseline/pingaccess` directory. We use environment variables for certain startup and runtime configuration settings of both standalone and orchestrated deployments. You can find environment variables that are common to all product images in the [PingBase Image Directory](../docker-images/pingbase/README.html). There are also product-specific environment variables. You can find these in the [Docker Image Information](../docker-images/dockerImagesRef.html) for each available product. ## Before you begin You must: * Complete [Get Started](../get-started/introduction.html) to set up your DevOps environment and run a test deployment of the products. * Understand the [Anatomy of the Product Containers](containerAnatomy.html). ### About this task You will: * Add or change the environment variables used for any of our server profiles to better fit your purposes. You can find these variables in the [Server Profiles Repository](https://github.com/pingidentity/pingidentity-server-profiles) for each product. For example, the location for the `env_vars` file for PingAccess is located in the [baseline/pingaccess server profile](https://github.com/pingidentity/pingidentity-server-profiles/tree/master/baseline/pingaccess). * Modify one of our server profiles to reflect an existing Ping Identity product installation in your organization. You can do this by either: * Forking our server profiles repository (`https://github.com/pingidentity/pingidentity-server-profiles`) to your Github repository * Using local directories ### Adding or Changing Environment Variables 1. Select any environment variables to add from either: * The product-specific environment variables in the [Docker Images Information](../docker-images/dockerImagesRef.html) * The environment variables common to all of our products in the [PingBase Image Directory](../docker-images/pingbase/README.html) 2. From the `baseline`, `getting-started`, or `simple-sync` directories in the [Server Profiles Repository](https://github.com/pingidentity/pingidentity-server-profiles), select the product whose profile you want to modify. 3. Open the `env_vars` file associated with the product and either: * Add any of the environment variables you've selected. * Change the existing environment variables to fit your purpose. ### Modifying a Server Profile You can modify one of our server profiles based on data from your existing Ping Identity product installation. Modify a server profile by either: * Using your Github repository * Using local directories #### Using Your Github Repository In this example PingFederate installation, using the Github Repository uses a server profile provided through a Github URL and assigned to the `SERVER_PROFILE_PATH` environment variable, such as `--env SERVER_PROFILE_PATH=getting-started/pingfederate`). 1. Export a [configuration archive](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_configurationarchivetasklet_selectimportexportstate.html) as a \*.zip file from a PingFederate installation to a local directory. > Make sure this is *exported* as a .zip rather than compressing it yourself. 2. Sign on to Github and fork into your own GitHub repository. 3. Open a terminal, create a new directory, and clone your Github repository to a local directory. For example: ```shell mkdir /tmp/pf_to_docker cd /tmp/pf_to_docker git clone https://github.com//pingidentity-server-profiles.git ``` Where `` is the name you used to sign on to the Github account. 4. Go to the location where you cloned your fork of our `pingidentity-server-profiles` repository, and replace the `/data` directory in `getting-started/pingfederate/instance/server/default` with the `data` directory you exported from your existing PingFederate installation. For example: ```shell cd pingidentity-server-profiles/getting-started/pingfederate/instance/server/default rm -rf data unzip -qd data /data.zip ``` Where `` is the location for your exported PingFederate configuration archive. You now have a local server profile based on your existing PingFederate installation. | | | | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | You should push to GitHub only what's necessary for your customizations. Our Docker images create the `/opt/out` directory using a product's base install and layering a profile (set of files) on top. | 5. Push your changes (your local server profile) to the Github repository where you forked our server profile repository. You now have a server profile available through a Github URL. 6. Deploy the PingFederate container. | | | | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | To save any changes you make after the container is running, add the entry `--volume :/opt/out` to the `docker run` command, where `` is a directory you haven't already created. For more information, see [Saving Your Changes](saveConfigs.html). | As in this example, the environment variables `SERVER_PROFILE_URL` and `SERVER_PROFILE_PATH` direct Docker to use the server profile you've modified and pushed to Github: ```shell docker run \ --name pingfederate \ --publish 9999:9999 \ --publish 9031:9031 \ --detach \ --env SERVER_PROFILE_URL=https://github.com//pingidentity-server-profiles.git \ --env SERVER_PROFILE_PATH=getting-started/pingfederate \ --env-file ~/.pingidentity/config \ pingidentity/pingfederate:edge ``` | | | | - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | If your GitHub server-profile repo is private, use the `username:token` format so the container can access the repository. For example, `https://github.com/:/pingidentity-server-profiles.git`. For more information, see [Using Private GitHub Repositories](privateRepos.html). | 7. To display the logs as the container starts up, enter: ```shell docker container logs -f pingfederate ``` 8. In a browser, go to to display the PingFederate console. #### Using Local Directories This method is particularly helpful when developing locally and the configuration isn't ready to be distributed (using Github, for example). We'll use PingFederate as an example. The local directories used by our containers to persist state and data, `/opt/in` and `/opt/out`, will be bound to another local directory and mounted as Docker volumes. This is our infrastructure for modifying the server profile. | | | | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | Docker recommends that you never use bind mounts in a production environment. This method is solely for developing server profiles. For more information, see the [Docker Documentation](https://docs.docker.com/storage/volumes/). | * The `/opt/out` directory All configurations and changes during our container runtimes (persisted data) are captured here. For example, the PingFederate image `/opt/out/instance` contains much of the typical PingFederate root directory: ```text . ├── README.md ├── SNMP ├── bin ├── connection_export_examples ├── etc ├── legal ├── lib ├── log ├── modules ├── sbin ├── sdk ├── server ├── tools └── work ``` * The `/opt/in` directory If a mounted `opt/in` directory exists, our containers reference this directory at startup for any server profile structures or other relevant files. This method is in contrast to a server profile provided using a Github URL assigned to the `SERVER_PROFILE_PATH` environment variable, such as, `--env SERVER_PROFILE_PATH=getting-started/pingfederate`. > For the data each product writes to a mounted `/opt/in` directory, see [Server profile structures](../reference/profileStructures.html). These directories are useful for building and working with local server-profiles. The `/opt/in` directory is particularly valuable if you don't want your containers to access Github for data (the default for our server profiles). The following example deployment uses PingFederate. 1. Deploy PingFederate using our sample [getting-started Server Profile](https://github.com/pingidentity/pingidentity-server-profiles/tree/master/getting-started/pingfederate), and mount `/opt/out` to a local directory: ```shell docker run \ --name pingfederate \ --publish 9999:9999 \ --detach \ --env SERVER_PROFILE_URL=https://github.com/pingidentity/pingidentity-server-profiles.git \ --env SERVER_PROFILE_PATH=getting-started/pingfederate \ --env-file ~/.pingidentity/config \ --volume /tmp/docker/pf:/opt/out \ pingidentity/pingfederate:edge ``` > Make sure the local directory (in this case, `/tmp/docker/pf`) isn't already created. Docker needs to create this directory for the mount to `/opt/out`. 2. Go to the mounted local directory (in this case, `/tmp/docker/pf`), then make and save some configuration changes to PingFederate using the management console. As you save the changes, you'll be able to see the files in the mounted directory change. For PingFederate, an `instance` directory is created. This is a PingFederate server profile. 3. Stop and remove the container and start a new container, adding another `/tmp/docker/pf` bind mounted volume, this time to `/opt/in`: ```shell docker container rm pingfederate docker run \ --name pingfederate-local \ --publish 9999:9999 \ --detach \ --volume /tmp/docker/pf:/opt/out \ --volume /tmp/docker/pf:/opt/in \ pingidentity/pingfederate:edge ```