Use a Docker Image and Start It by Changing the Parameters from the Default Values
Overview¶
This is the procedure for specifying PostgreSQL as the database, changing the parameters from their default values, and starting Pleasanter from the official Docker image.
Limitations¶
- When you perform this procedure with ver1.4.5 or earlier, the CodeDefiner command is different. Refer to the following page.
About the CodeDefiner procedure when installing for the first time from version 1.4.6 - The procedure on this page uses a multi-container configuration that includes the PostgreSQL container in the same Docker configuration as Pleasanter, for users who want to try Pleasanter right away. This configuration is not intended for production use.
- In production use, the database container becomes a performance bottleneck. We strongly recommend using a database on a separate host.
Prerequisites¶
- This procedure uses PostgreSQL as the database. For the procedure using another database, refer to the following.
- This procedure assumes that Docker is available as described in the manual below.
Refer to the manual below and check that you can start Pleasanter using the official Docker image of Pleasanter. - When you use PostgreSQL as the database, you do not need to place or edit Rds.json.
Operation Procedure¶
1. Placing Files and Creating Folders¶
Configure the folders in the project directory (pleasanter in the example below) as follows and place the files.
📁pleasanter
+-- 📁app_data_parameters
| +-- 📁folder for extended features
| | +-- 📄file for extended features
| |
| +-- 📄parameter file
|
|-- 📄.env
|-- 📄compose.yaml
| Folder or file | Description |
|---|---|
| app_data_parameters | A folder for storing the parameter files configured for your environment. Store the folders and files for extended features, such as extended SQL and extended scripts, in this folder as well if necessary. |
| .env | A file that describes settings such as the database connection information, and environment variables |
| compose.yaml | The configuration file of Docker Compose |
1-1. Creating the app_data_parameters Folder¶
-
Run the following command in the project directory to create the
app_data_parametersfolder.
1-2. Preparing the Parameter Files¶
- Download Pleasanter from the Download Center. Unless you have a particular reason, download the latest version. If you need a specific version released in the past, download that version of Pleasanter.
- Extract the zip file to any location.
- From "
\pleasanter\Implem.Pleasanter\App_Data\Parameters" in the extracted folder, copy the parameters you want to change under theapp_data_parametersfolder created in 1-1. - Change the contents of the parameters as necessary and update them.
- When you configure extended features such as extended SQL (ExtendedSqls) or extended scripts (ExtendedScripts), copy the folders for the extended features to
app_data_parameters, and create the files for the extended features in each copied folder.
1-3 The .env File¶
-
Run the following command to create the
.envfile. -
Open
.envin a text editor, paste the following content, and save it. Modify{{ ... }}as necessary for your environment. For each setting, refer to the description of the.envfile in "Launch with Docker".
1-4 The compose.yaml File¶
-
Run the following command to create the compose.yaml file.
-
Open
compose.yamlin a text editor, paste the following content, and save it.
2. Restarting Pleasanter¶
-
If Pleasanter is running, run the following command to stop Pleasanter.
-
Run the following command to clear the volume for the parameters. Modify {{Project directory name}} as necessary for your environment. If the volume for the parameters does not exist, for example when you run this procedure for the first time, an error stating that the volume does not exist is returned, but continue from step 3.
Example: when the project directory is "pleasanter", the command is as follows.
-
Run the following command to start Pleasanter.
3. Logging In to Pleasanter¶
-
Access Pleasanter in a browser, and log in by entering your login ID and password on the login screen.
-
Check that the parameters you set have been applied.
4. When Running CodeDefiner After Changing the Parameters¶
When you run CodeDefiner after setting the parameters, for example when you use the "System Log Extended Function", run it with the following procedure.
- Perform "1. Placing Files and Creating Folders" and store the changed parameter files in app_data_parameters.
-
If Pleasanter is running, run the following command to stop Pleasanter.
-
Run the following command to clear the volume for the parameters. Modify {{Project directory name}} as necessary for your environment.
Example: when the project directory is "pleasanter", the command is as follows.
-
Run CodeDefiner.