How to self-host GroupDocs.Editor Cloud with Docker Leave feedback
On this page
Docker is an open platform that effectively solves three main tasks development, deployment, and running the applications. With Docker, you can isolate your applications from the infrastructure that simplifies software development and delivery. The main building blocs are images and containers. The image includes everything you need to run the application: code or binaries, runtime dependencies, file system. The container is an isolated process with additional features that you can interact with. The use of containers to deploy applications is called containerization.
Docker Hub is a repository or library of the container images where you can share and find images.
The GroupDocs.Editor Cloud Container Image available at https://hub.docker.com/r/groupdocs/editor-cloud and enables users to self-host GroupDocs.Editor Cloud.
To run the GroupDocs.Editor Cloud in Docker the Docker itself should be installed on your machine.
Check Get Started section for Docker installation for your platform. After you installed and started Docker on your local machine we can run the container.
NoteWhen running Docker on Windows make sure to switch to Linux containers by clicking on Docker icon in the tray and selecting “Switch to Linux containers…” (see https://docs.docker.com/docker-for-windows/#switch-between-windows-and-linux-containers for more details.)
Before running the container you can create two optional folders with files to process and custom fonts that we’ll be mounted and available to GroupDocs.Editor Cloud service when we start the container.
To run GroupDocs.Editor Cloud in Docker type one of the following commands:
NoteIn case you don’t have license keys you can omit LICENSE_PUBLIC_KEY and LICENSE_PRIVATE_KEY parameters. Without license GroupDocs.Editor will work in evaluation mode.
docker run `
В В -p 8080:80 `
В В -v "${pwd}/data:/data" `
В В -e "LICENSE_PUBLIC_KEY#public_key" `
В В -e "LICENSE_PRIVATE_KEY#private_key" `
В В --name editor_cloud `
В В groupdocs/editor-cloud
docker run \
В В В В -p 8080:80 \
В В В В -v $(pwd)/data:/data \
В В В В -e LICENSE_PUBLIC_KEY#public_key \
В В В В -e LICENSE_PRIVATE_KEY#private_key \
В В В В --name editor_cloud \
В В В В groupdocs/editor-cloud
The Docker would download GroupDocs.Editor Cloud image from Docker Hub and start a container.
NoteI’m running Docker on Windows and will be using PowerShell to run the commands but the experience would be the same in case you’re on Linux.
After the container is started you’ll see the following messages that indicate that GroupDocs.Editor Cloud service up and running.
Now you can work with GroupDocs.Editor Cloud which is hosted on your machine.
When the container and GroupDocs.Editor Cloud started you can check service status by calling GET http://localhost:8080/. The successful response status (200) will indicate that the service is up and running.
Invoke-WebRequest -Uri http://localhost:8080/
curl -i http://localhost:8080/
At the following screenshot, I’m calling http://localhost:8080/ in a separate Powershell window and response indicates that service is alive:
After starting, you can use Swagger UI at http://localhost:8080/swagger/ and explore the API. With Swagger UI you can call API methods in your browser.
We generate our SDKs in different languages so you may check if yours is available at GitHub. SDKs require authentication, so predefined CLIENT_ID/CLIENT_SECRET parameters must be set.
NoteIf you don’t find your language in the SDK list, feel free to request for it on our Support Forums, or use raw REST API requests as you can find it here.
The authentication is required in case you’re going to use SDK. To enable authentication set CLIENT_ID/CLIENT_SECRET parameters as it shown below.
docker run `
В В В В -p 8080:80 `
В В В В -v "${pwd}/data:/data" `
В В В В -e "LICENSE_PUBLIC_KEY#public_key" `
В В В В -e "LICENSE_PRIVATE_KEY#private_key" `
В В В В -e "client_id=client_id" `
В В В В -e "client_secret=client_secret" `
В В В В --name editor_cloud `
В В В В groupdocs/editor-cloud
docker run \
В В В В -p 8080:80 \
В В В В -v $(pwd)/data:/data \
В В В В -e LICENSE_PUBLIC_KEY#public_key \
В В В В -e LICENSE_PRIVATE_KEY#private_key \
В В В В -e client_id=client_id \
В В В В -e client_secret=client_secret \
В В В В --name editor_cloud \
В В В В groupdocs/editor-cloud
Then, when using SDK, setup the api base url, as shown in examples below:
// For complete examples and data files, please go to https://github.com/groupdocs-editor-cloud/groupdocs-editor-cloud-dotnet-samples
string ClientId = ""; // Get ClientId and ClientSecret from https://dashboard.groupdocs.cloud
string ClientSecret = ""; // Get ClientId and ClientSecret from https://dashboard.groupdocs.cloud
var configuration = new Configuration(ClientId, ClientSecret)
{
ApiBaseUrl = "http://localhost:8080"
};
var apiInstance = new InfoApi(configuration);
var response = apiInstance.GetSupportedFileFormats();
// For complete examples and data files, please go to https://github.com/groupdocs-editor-cloud/groupdocs-editor-cloud-java-samples
String ClientId = ""; // Get ClientId and ClientSecret from https://dashboard.groupdocs.cloud
String ClientSecret = ""; // Get ClientId and ClientSecret from https://dashboard.groupdocs.cloud
Configuration configuration = new Configuration(ClientId, ClientSecret);
configuration.setApiBaseUrl("http://localhost:8080");
InfoApi apiInstance = new InfoApi(configuration);
FormatsResult response = apiInstance.getSupportedFileFormats();
// For complete examples and data files, please go to https://github.com/groupdocs-editor-cloud/groupdocs-editor-cloud-php-samples
use GroupDocs\Editor\Model;
use GroupDocs\Editor\Model\Requests;
$ClientId = ""; // Get ClientId and ClientSecret from https://dashboard.groupdocs.cloud
$ClientSecret = ""; // Get ClientId and ClientSecret from https://dashboard.groupdocs.cloud
$configuration = new GroupDocs\Editor\Configuration();
$configuration->setAppSid($ClientId);
$configuration->setAppKey($ClientSecret);
$configuration->setApiBaseUrl("http://localhost:8080");
$infoApi= new GroupDocs\Editor\InfoApi($configuration);
$response = $infoApi->getSupportedFileFormats();
// For complete examples and data files, please go to https://github.com/groupdocs-editor-cloud/groupdocs-editor-cloud-node-samples
global.editor_cloud = require("groupdocs-editor-cloud");
global.clientId = "XXXX-XXXX-XXXX-XXXX"; // Get ClientId and ClientSecret from https://dashboard.groupdocs.cloud
global.clientSecret = "XXXXXXXXXXXXXXXX"; // Get ClientId and ClientSecret from https://dashboard.groupdocs.cloud
const config = new Configuration(clientId, clientSecret);
config.apiBaseUrl = "http://localhost:8080";
global.infoApi = editor_cloud.InfoApi.fromConfig(config);
let response = await infoApi.getSupportedFileFormats();
# For complete examples and data files, please go to https://github.com/groupdocs-editor-cloud/groupdocs-editor-cloud-python-samples
import groupdocs_editor_cloud
client_id = "XXXX-XXXX-XXXX-XXXX" # Get ClientId and ClientSecret from https://dashboard.groupdocs.cloud
client_secret = "XXXXXXXXXXXXXXXX" # Get ClientId and ClientSecret from https://dashboard.groupdocs.cloud
configuration = Configuration(client_id, client_secret)
configuration.api_base_url = "http://localhost:8080"
infoApi = groupdocs_editor_cloud.InfoApi.from_config(configuration)
result = infoApi.get_supported_file_formats()
# For complete examples and data files, please go to https://github.com/groupdocs-editor-cloud/groupdocs-editor-cloud-ruby-samples
require 'groupdocs_editor_cloud'
$client_id = "XXXX-XXXX-XXXX-XXXX" # Get ClientId and ClientSecret from https://dashboard.groupdocs.cloud
$client_secret = "XXXXXXXXXXXXXXXX" # Get ClientId and ClientSecret from https://dashboard.groupdocs.cloud
config = Configuration.new(client_id, client_secret)
config.api_base_url = "http://localhost:8080"
infoApi = GroupDocsEditorCloud::InfoApi.from_config(config)
result = infoApi.get_supported_file_formats()
By default, a local storage used inside container for file operations. It’s possible to connect a Google Cloud storage by setting GOOGLE_APPLICATION_CREDENTIALS and GOOGLE_STORAGE_BUCKET environment variables.
docker run `
В В В В -p 8080:80 `
В В В В -v "${pwd}/data:/data" `
В В В В -e "GOOGLE_APPLICATION_CREDENTIALS=/data/key.json" `
В В В В -e "GOOGLE_STORAGE_BUCKET=bucket_id" `
В В В В --name editor_cloud `
В В В В groupdocs/editor-cloud
docker run \
В В В В -p 8080:80 \
В В В В -v $(pwd)/data:/data \
В В В В -e GOOGLE_APPLICATION_CREDENTIALS=/data/key.json \
В В В В -e GOOGLE_STORAGE_BUCKET=bucket_id \
В В В В --name editor_cloud \
В В В В groupdocs/editor-cloud
To stop the running Docker container, just use Ctrl+C in the same terminal where the container is running. Alternatively, you can stop the container by name.
docker stop editor_cloud
GroupDocs.Editor Cloud can be started in trial and licensed modes. When GroupDocs.Editor Cloud is working in trial mode the following limitations are applied:
- You can compare only two first pages of the document
- Evaluation watermarks added to the output
You can find more information at DockerHub.
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.
