Applipress Configuration
Configuring Automatic Translation for Generated Forms
To facilitate the development of multilingual applications, Applipress offers an automatic translation feature for generated forms. This feature allows your forms to be seamlessly translated into other languages, enhancing the accessibility and global reach of your application. To enable and configure this functionality, follow the steps below:
-
Access the Configuration File: Navigate to the
./config/auto-translate/.auto-translate-config.jsonfile in your project directory. This file contains the settings necessary to configure the automatic translation feature. -
Enable Automatic Translation: In the
.auto-translate-config.jsonfile, find theautomaticTranslationsetting. Change its value totrueto activate the automatic translation feature."automaticTranslation": true, -
Set Up Translation Service Key: Depending on the translation service you wish to use, enter your API key into the appropriate field:
-
For Google Translate, fill in your API key in the
googleTranslateKeyfield. -
For Microsoft Azure Translation, use the
azureTranslateKeyfield.
"googleTranslateKey": "your_google_translate_api_key_here", "azureTranslateKey": "your_azure_translate_api_key_here", -
-
Select the Translation Provider: Set the
translatorProviderfield to eithergoogleorazure, depending on which service's API key you provided in the previous step."translatorProvider": "google", -
Save the Configuration File: After entering your API key and ensuring that automatic translation is enabled, save the
.auto-translate-config.jsonfile. Your changes will take effect the next time you generate forms using Applipress.
Additional Notes:
-
Obtaining API Keys: To use automatic translation services, you must have a valid API key from either Google or Azure. You can obtain these keys by creating an account on their respective platforms and setting up a translation service.
-
Translation Costs: Keep in mind that the use of translation APIs may incur costs. Check the pricing details on the Google Cloud or Azure Portal to understand the potential expenses based on your usage.
By following these steps, you enable the automatic translation of your generated forms, making your applications accessible to a broader audience with minimal effort.
Specifying the generated projects directory
One of the key configurations that Applipress users often wish
to customize is the mapping of the
./projects directory
to a directory on their own system. This allows for easier
management and access to the projects created by Applipress.
Here's how to customize this mapping in the
docker-compose.yml
file:
In the
docker-compose.yml
file, you will find a section under the
volumes attribute of
the
applipress service
that looks like this:
To map the
./projects directory
to a specific directory on your system, such as
/home/users/projects, simply replace
./projects with the
desired path on the left side of the colon. For example:
This modification tells Docker to map the local directory
/home/users/projects
to the
/projects directory
inside the Docker container. This means that any projects
created or managed by Applipress in the container will be
accessible in
/home/users/projects
on your local system.
Important Considerations
-
Absolute Path: Ensure you use the absolute path to the directory on your system when configuring the volume mapping.
-
Permissions: Make sure that the directory on your local system has the appropriate permissions for reading, writing, and executing as needed by Applipress.
-
Existing Data: If there are existing projects in
/home/users/projects, they will be accessible to Applipress. Likewise, new projects created by Applipress will appear in this directory.
By customizing the volume mapping for the projects directory, you gain flexibility in how and where you store your Applipress projects, making it easier to integrate Applipress into your existing workflow and project management practices.