diff --git a/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-documenteditor-java-web-api-in-azure.md b/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-documenteditor-java-web-api-in-azure.md index f5e83f74b2..aedb59600d 100644 --- a/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-documenteditor-java-web-api-in-azure.md +++ b/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-documenteditor-java-web-api-in-azure.md @@ -1,13 +1,13 @@ --- layout: post -title: How to deploy documenteditor java web api in azure in Vue Document editor component | Syncfusion +title: How to Deploy Vue DOCX Editor Java Web API in Azure App | Syncfusion description: Learn here all about How to deploy documenteditor java web api in azure in Syncfusion Vue Document editor component of Syncfusion Essential JS 2 and more. control: How to deploy documenteditor java web api in azure platform: document-processing documentation: ug domainurl: ##DomainURL## --- -# How to deploy documenteditor java web api in azure in Vue Document editor component +# How to Deploy Vue DOCX Editor Java Web API in Azure App ## Prerequisites @@ -15,19 +15,19 @@ Have [`Azure account`](https://azure.microsoft.com/en-gb/) and [`Azure CLI`](htt You can get the example [`web service project from GitHub`](https://github.com/SyncfusionExamples/EJ2-DocumentEditor-Java-WebService) and then perform the following steps to create the packages and host in azure app service. -**Step 1** Clean the package using following command. +**Step 1:** Clean the package using the following command. ```console mvn clean package ``` -**Step 2** Run the application locally using following command. +**Step 2:** Run the application locally using the following command. ```console mvn spring-boot:run ``` -**Step 3** Build the package using following command. +**Step 3:** Build the package using the following command. ```console mvn package @@ -37,26 +37,26 @@ Above package generation command creates the `**tomcat-0.0.1-SNAPSHOT.war**` in `target/tomcat-0.0.1-SNAPSHOT.war` -**Step 4:** Create a Azure app service with Java & Tomcat. For example, create the app services name as `documenteditorjava`. +**Step 4:** Create an Azure App Service with Java & Tomcat. For example, create the App Service with name `documenteditorjava`. -**Step 5:** After creating app service, navigate to `Advanced Tools` options under `Development Tools`. +**Step 5:** After creating the App Service, navigate to `Advanced Tools` options under `Development Tools`. -![Advanced tools ](../images/azure_java_advancedtools.png) +![Azure Java Advanced tools](../images/azure_java_advancedtools.png) -Then, click `Go` and select the `CMD` options under `Debug console`. +Then, click `Go` and select the `CMD` option under `Debug console`. -![Debug console ](../images/azure_java_debugconsole.png) +![Debug console](../images/azure_java_debugconsole.png) -**Step 6**: Once the file manager is opened, please navigate to +**Step 6:** Once the file manager is opened, navigate to: `site -> wwwroot -> webapps` -**Step 7**: Now, upload the generated war file `tomcat-0.0.1-SNAPSHOT.war`. Uploaded war file gets extracted automatically, it will uploaded like below: +**Step 7:** Now, upload the generated WAR file `tomcat-0.0.1-SNAPSHOT.war`. It is extracted automatically, as shown below: -![Uploaded war](../images/java_azure_uploaded.png) +![Uploaded war file](../images/java_azure_uploaded.png) **Step 8:** Browse to the app. -Browse to the deployed app at `http://.azurewebsites.net`, i.e. `http://documenteditorjava.azurewebsites.net`. Browse this link and it navigate to the Document Editor Web API control `http://documenteditorjava.azurewebsites.net/tomcat-0.0.1-SNAPSHOT`. It returns the default get method response. +Browse to the deployed app at `http://.azurewebsites.net`, i.e., `http://documenteditorjava.azurewebsites.net`. Browse this link and it navigates to the Document Editor Web API control `http://documenteditorjava.azurewebsites.net/tomcat-0.0.1-SNAPSHOT`. It returns the default GET method response. -Append the app service running the URL `http://documenteditorjava.azurewebsites.net/tomcat-0.0.1-SNAPSHOT` to the service URL in the client-side Document Editor control. For more information about the Document Editor control, refer to this [`getting started page`](../getting-started). \ No newline at end of file +Append the App Service running URL `http://documenteditorjava.azurewebsites.net/tomcat-0.0.1-SNAPSHOT` to the service URL in the client-side Document Editor control. For more information about the Document Editor control, refer to this [`getting started page`](../getting-started). \ No newline at end of file diff --git a/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-word-processor-server-docker-container-in-amazon-kubernetes-service.md b/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-word-processor-server-docker-container-in-amazon-kubernetes-service.md index cdcc8487eb..36aee06a76 100644 --- a/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-word-processor-server-docker-container-in-amazon-kubernetes-service.md +++ b/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-word-processor-server-docker-container-in-amazon-kubernetes-service.md @@ -1,38 +1,38 @@ --- layout: post -title: Deploy Syncfusion Word Processor in Amazon Kubernetes Service -description: Learn here all about How to deploy word processor server docker container in amazon kubernetes service in Syncfusion Document editor. +title: Deploy Vue DOCX Editor Docker on Amazon Kubernetes | Syncfusion +description: Deploy the Syncfusion® Vue DOCX Editor Docker image to Amazon Kubernetes Service for scalable and reliable document processing. control: How to deploy word processor server docker container in amazon kubernetes service platform: document-processing documentation: ug domainurl: ##DomainURL## --- -# How to deploy Word Processor server in Amazon Kubernetes Service +# How to Deploy Vue DOCX Editor Docker Image on Amazon Kubernetes ## Prerequisites -* `AWS Account` :Have Amazon account +* `AWS Account`: Have an Amazon account. * `AWS CLI`: Install the AWS Command Line Interface (CLI) on your local machine. -* `Kubectl` : Install the Kubernetes command-line tool kubectl on your local machine. +* `Kubectl`: Install the Kubernetes command-line tool kubectl on your local machine. * `Docker`: Install Docker on your local machine. * `Word Processor Docker Image`: Have a Docker image of the Word Processor server ready to deploy. -To deploy the Word Processor server docker image, need to follow the below process +To deploy the Word Processor server docker image, you need to follow the process below. * Push Docker Image to Registry (Amazon Elastic Registry) * Deploy Docker Image on Amazon Kubernetes Service -Lets us discuss briefly about the each process +Let us briefly discuss each process. ## Push the Docker image to the Amazon Elastic Registry **Step 1:** Dockerize the Word Processor Server Application with the image name [syncfusion/word-processor-server](https://hub.docker.com/r/syncfusion/word-processor-server) ``` -docker build -t +docker build -t . ``` -**Step 2:** Create a private repository name ‘document editor’ in Amazon Elastic Container Registry (ECR) using the AWS CLI or AWS Console to push the docker image +**Step 2:** Create a private repository named 'documenteditor' in Amazon Elastic Container Registry (ECR) using the AWS CLI or AWS Console. ``` aws ecr create-repository --repository-name @@ -43,13 +43,13 @@ aws ecr create-repository --repository-name ``` docker tag :latest /:latest ``` -Refer to the following example to tag the image +Refer to the following example to tag the image. ``` docker tag syncfusion/word-processor-server:latest 123456.dkr.ecr.us-east-1.amazonaws.com/documenteditor:latest ``` -> Get the ECR registry URI from AWS console or using the below AWS CLI command +N> Get the ECR registry URI from AWS console or using the below AWS CLI command. ``` aws ecr describe-repositories --repository-names --query 'repositories[*].repositoryUri' --output text @@ -71,17 +71,18 @@ docker push /:latest ## Deploy Docker Image on Amazon Kubernetes Service -Follow the below steps to deploy the Docker image from the Amazon Elastic Registry( ECR) to Amazon Kubernetes Services (EKS) +Follow the below steps to deploy the Docker image from the Amazon Elastic Registry (ECR) to Amazon Kubernetes Services (EKS). -**Step 1:** DCreate Amazon EKS cluster using the AWS Console +**Step 1:** Create an Amazon EKS cluster using the AWS Console. -**Step 2:** Authenticate with AWS ECR -Need to get the authenticate with the AWS ECR to pull the image from the registry +**Step 2:** Authenticate with AWS ECR. + +You need to authenticate with the AWS ECR to pull the image from the registry. ``` aws ecr get-login-password --region | docker login --username AWS --password-stdin .dkr.ecr..amazonaws.com ``` - +Configure Kubernetes to communicate with the cluster. **Step 3:** : Configure Kubernetes to Communicate with the Cluster ``` @@ -104,11 +105,11 @@ In this command: * should be replaced with your AWS region. -**Step 5:** To create Kubernetes deployment write Kubernetes manifest +**Step 5:** To create a Kubernetes deployment, write a Kubernetes manifest. **i.** Create a Kubernetes Deployment manifest (deployment.yaml) for your application. Specify the Docker image location. -``` +```yaml apiVersion: apps/v1 kind: Deployment metadata: @@ -129,22 +130,22 @@ spec: ports: - containerPort: 80 ``` -**ii.** Apply the Deployment manifest to create the deployment in your EKS cluster +**ii.** Apply the Deployment manifest to create the deployment in your EKS cluster. ``` kubectl apply -f deployment.yaml ``` -**iii.** Use port forwarding to access the Word Processor Server application locally and verify its functionality +**iii.** Use port forwarding to access the Word Processor Server application locally and verify its functionality. ``` kubectl port-forward pod-name local-port:container-port ``` -> Get the pod names in AWS Console or using the below AWS CLI command +N> Get the pod names in AWS Console or using the below AWS CLI command. ``` kubectl get pods ``` -Finally you can get the sample in the localhost http://``````/api/documenteditor/ \ No newline at end of file +Finally, you can access the sample at localhost: http:///api/documenteditor/ \ No newline at end of file diff --git a/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-word-processor-server-docker-container-in-azure-app-service.md b/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-word-processor-server-docker-container-in-azure-app-service.md index f80f441fa5..e8a0181098 100644 --- a/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-word-processor-server-docker-container-in-azure-app-service.md +++ b/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-word-processor-server-docker-container-in-azure-app-service.md @@ -1,13 +1,13 @@ --- layout: post -title: How to deploy word processor server docker container in azure app service in Vue Document editor component | Syncfusion -description: Learn here all about How to deploy word processor server docker container in azure app service in Syncfusion Vue Document editor component of Syncfusion Essential JS 2 and more. +title: How to Deploy Vue DOCX Editor Docker image on Azure App | Syncfusion +description: Deploy the Syncfusion® Vue DOCX Editor Docker image to Azure App Service for scalable and reliable document processing. control: How to deploy word processor server docker container in azure app service platform: document-processing documentation: ug domainurl: ##DomainURL## --- -# How to deploy word processor server docker container in azure app service in Vue Document editor component +# How to Deploy Vue DOCX Editor Docker image on Azure App ## Prerequisites @@ -22,7 +22,7 @@ domainurl: ##DomainURL## Create a resource group using the [`az group create`](https://docs.microsoft.com/en-us/cli/azure/group#az-group-create) command. -The following example creates a resource group named documenteditorresourcegroup in the eastus location. +The following example creates a resource group named documenteditorresourcegroup in the East US location. ``` az group create --name documenteditorresourcegroup --location "East US" @@ -40,7 +40,7 @@ az appservice plan create --name documenteditorappservice --resource-group docum **Step 3:** Create a Docker Compose app. -Create a multi-container [`web app`](https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-intro) in the documenteditorappservice App Service plan with the [`az webapp create`](https://docs.microsoft.com/en-us/cli/azure/webapp?view=azure-cli-latest#az-webapp-create) command. The following command creates the web app using the provided Docker compose file. Please look into the section for getting started with Docker compose to create the Docker compose file for the document editor server and use the created Docker compose file here. +Create a multi-container [`web app`](https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-intro) in the documenteditorappservice App Service plan with the [`az webapp create`](https://docs.microsoft.com/en-us/cli/azure/webapp?view=azure-cli-latest#az-webapp-create) command. The following command creates the web app using the provided Docker Compose file. Refer to the Docker Compose getting started section to create the Docker Compose file for the Document Editor server and use the created Docker Compose file here. ``` az webapp create --resource-group documenteditorresourcegroup --plan documenteditorappservice --name documenteditor-server --multicontainer-config-type compose --multicontainer-config-file documenteditor-server-compose.yml @@ -48,8 +48,8 @@ az webapp create --resource-group documenteditorresourcegroup --plan documentedi **Step 4:** Browse to the app. -Browse to the deployed app at `http://.azurewebsites.net`, i.e. `http://documenteditor-server.azurewebsites.net`. Browse this link and navigate to the Document Editor Web API control `http://documenteditor-server.azurewebsites.net/api/documenteditor`. It returns the default get method response. +Browse to the deployed app at `http://.azurewebsites.net`, i.e., `http://documenteditor-server.azurewebsites.net`. Open this link and navigate to the Document Editor Web API control `http://documenteditor-server.azurewebsites.net/api/documenteditor`. It returns the default GET method response. -Append the app service running the URL `http://documenteditor-server.azurewebsites.net/api/documenteditor/` to the service URL in the client-side Document Editor control. For more information about the Document Editor control, refer to this [`getting started page`](../getting-started). +Append the app service running URL `http://documenteditor-server.azurewebsites.net/api/documenteditor/` to the service URL in the client-side Document Editor control. For more information about the Document Editor control, refer to this [`getting started page`](../getting-started). -For more information about the app container service, please look deeper into the [`Microsoft Azure Container Service`](https://docs.microsoft.com/en-us/azure/app-service/containers/quickstart-multi-container) for a production-ready setup. +For more information about the app container service, refer to the [`Azure App Service`](https://docs.microsoft.com/en-us/azure/app-service/containers/quickstart-multi-container) for a production-ready setup. diff --git a/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-word-processor-server-docker-container-in-azure-kubernetes-service.md b/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-word-processor-server-docker-container-in-azure-kubernetes-service.md index 5efd579020..4102d4bc08 100644 --- a/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-word-processor-server-docker-container-in-azure-kubernetes-service.md +++ b/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-deploy-word-processor-server-docker-container-in-azure-kubernetes-service.md @@ -1,13 +1,13 @@ --- layout: post -title: How to deploy word processor server docker container in azure kubernetes service in Vue Document editor component | Syncfusion -description: Learn here all about How to deploy word processor server docker container in azure kubernetes service in Syncfusion Vue Document editor component of Syncfusion Essential JS 2 and more. +title: How to Deploy Vue DOCX Editor Docker image on AKS | Syncfusion +description: Deploy the Syncfusion® Vue DOCX Editor Docker image to Azure Kubernetes Service (AKS) for scalable and reliable document processing. control: How to deploy word processor server docker container in azure kubernetes service platform: document-processing documentation: ug domainurl: ##DomainURL## --- -# How to deploy word processor server docker container in azure kubernetes service in Vue Document editor component +# How to Deploy Vue DOCX Editor Docker Image on AKS ## Prerequisites @@ -22,7 +22,7 @@ domainurl: ##DomainURL## Create a resource group using the [`az group create`](https://docs.microsoft.com/en-us/cli/azure/group#az-group-create) command. -The following example creates a resource group named documenteditorresourcegroup in the eastus location. +The following example creates a resource group named documenteditorresourcegroup in the East US location. ``` az group create --name documenteditorresourcegroup --location "East US" @@ -38,7 +38,7 @@ az aks create --resource-group documenteditorresourcegroup --name documenteditor **Step 3:** Connect to the cluster. -Install the [`kubectl`](https://kubernetes.io/docs/reference/kubectl/kubectl/) into the workspace using the following command. +Install [`kubectl`](https://kubernetes.io/docs/reference/kubectl/kubectl/) using the following command. ``` az aks install-cli @@ -108,8 +108,8 @@ Run the following command to get the Kubernetes cluster deployed service details kubectl get all ``` -Browse the copied external IP address and navigate to the Document Editor Web API control `http:///api/documenteditor`. It returns the default get method response. +Browse to the copied external IP address and navigate to the Document Editor Web API control `http:///api/documenteditor`. It returns the default GET method response. -**Step 6:** Append the Kubernetes service running the URL `http:///api/documenteditor/` to the service URL in the client-side Document Editor control. For more information about the Document Editor control, refer to this [`getting started page`](../getting-started). +**Step 6:** Append the Kubernetes service running URL `http:///api/documenteditor/` to the service URL in the client-side Document Editor control. For more information about the Document Editor control, refer to this [`getting started page`](../getting-started). For more details about the Azure Kubernetes service, please look deeper into [`Microsoft Azure Kubernetes Service`](https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough) for a production-ready setup. diff --git a/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-publish-documenteditor-web-api-application-in-azure-app-service-from-visual-studio.md b/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-publish-documenteditor-web-api-application-in-azure-app-service-from-visual-studio.md index 4622f6bc4d..8fa1271450 100644 --- a/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-publish-documenteditor-web-api-application-in-azure-app-service-from-visual-studio.md +++ b/Document-Processing/Word/Word-Processor/vue/server-deployment/how-to-publish-documenteditor-web-api-application-in-azure-app-service-from-visual-studio.md @@ -1,14 +1,14 @@ --- layout: post -title: How to publish documenteditor web api application in azure app service from visual studio in Vue Document editor component | Syncfusion -description: Learn here all about How to publish documenteditor web api application in azure app service from visual studio in Syncfusion Vue Document editor component of Syncfusion Essential JS 2 and more. +title: How to Publish Vue DOCX Editor Web API to Azure App | Syncfusion +description: Publish the Syncfusion® Vue DOCX Editor Web API to Azure App Service in React applications, including deployment and configuration steps. control: How to publish documenteditor web api application in azure app service from visual studio platform: document-processing documentation: ug domainurl: ##DomainURL## --- -# How to publish documenteditor web api application in azure app service from visual studio in Vue Document editor component +# How to Publish Vue DOCX Editor Web API to Azure App ## Prerequisites @@ -22,22 +22,22 @@ Make sure you build the project using the Build > Build Solution menu command be **Step 1:** In Solution Explorer, right-click the project and click Publish (or use the Build > Publish menu item). -![azure publish ](../images/azure_publish.png) +![Azure publish](../images/azure_publish.png) **Step 2:** If you have previously configured any publishing profiles, the Publish pane appears, in which case select Create new profile. **Step 3:** In the Pick a publish target dialog box, select App Service. -![azure target](../images/azure_target.png) +![Azure target](../images/azure_target.png) **Step 4:** Select Publish. The Create App Service dialog box appears. Sign in with your Azure account, if necessary, and then the default app service settings populate the fields. -![azure documenteditor](../images/azure_documenteditor.png) +![Azure documenteditor](../images/azure_documenteditor.png) -**Step 5:** Select Create. Visual Studio deploys the app to your Azure App Service, and the web app loads in your browser with the app name at `http://.azurewebsites.net` (i.e. `http://ej2-documenteditor-server20200514102909.azurewebsites.net`). +**Step 5:** Select Create. Visual Studio deploys the app to your Azure App Service, and the web app loads in your browser with the app name at `http://.azurewebsites.net` (i.e., `http://ej2-documenteditor-server20200514102909.azurewebsites.net`). -**Step 6:** Navigate to Document Editor Web API control `http://ej2-documenteditor-server20200514102909.azurewebsites.net/api/documenteditor`. It returns the default get method response. +**Step 6:** Navigate to Document Editor Web API control `http://ej2-documenteditor-server20200514102909.azurewebsites.net/api/documenteditor`. It returns the default GET method response. -Append the app service running the URL `http://ej2-documenteditor-server20200514102909.azurewebsites.net/api/documenteditor` to the service URL in the client-side Document Editor control. For more information about how to get started with the Document Editor control, refer to this [`getting started page`](../getting-started). +Append the app service running URL `http://ej2-documenteditor-server20200514102909.azurewebsites.net/api/documenteditor` to the service URL in the client-side Document Editor control. For more information about how to get started with the Document Editor control, refer to this [`getting started page`](../getting-started). -For more information about the app container service, please look deeper into the [`Microsoft Azure App Service`](https://docs.microsoft.com/en-us/visualstudio/deployment/) for a production-ready setup. +For more information about the app container service, refer to the [`Azure App Service`](https://docs.microsoft.com/en-us/visualstudio/deployment/) for a production-ready setup. diff --git a/Document-Processing/Word/Word-Processor/vue/server-deployment/word-processor-server-docker-image-overview.md b/Document-Processing/Word/Word-Processor/vue/server-deployment/word-processor-server-docker-image-overview.md index e5659aa7ab..da45b58651 100644 --- a/Document-Processing/Word/Word-Processor/vue/server-deployment/word-processor-server-docker-image-overview.md +++ b/Document-Processing/Word/Word-Processor/vue/server-deployment/word-processor-server-docker-image-overview.md @@ -1,6 +1,6 @@ --- layout: post -title: Word processor server docker image overview in Vue Document editor component | Syncfusion +title: Docker image of Syncfusion Vue DOCX Editor Control| Syncfusion description: Learn here all about Word processor server docker image overview in Syncfusion Vue Document editor component of Syncfusion Essential JS 2 and more. control: Word processor server docker image overview platform: document-processing @@ -8,11 +8,11 @@ documentation: ug domainurl: ##DomainURL## --- -# Word processor server docker image overview in Vue Document editor component +# Docker Image of Syncfusion Vue DOCX Editor Control -The **[React DOCX Editor](https://www.syncfusion.com/docx-editor-sdk/react-docx-editor) (also known as Document Editor)** is a component with editing capabilities like Microsoft Word. It is used to create, edit, view, and print Word documents. It provides all the common word processing abilities, including editing text; formatting contents; resizing images and tables; finding and replacing text; importing, exporting, and printing Word documents; and using bookmarks and tables of contents. +The [Vue DOCX Editor](https://www.syncfusion.com/docx-editor-sdk/vue-docx-editor) (Document Editor) is a component with editing capabilities like Microsoft Word. It is used to create, edit, view, and print Word documents. It provides all the common word processing abilities, including editing text; formatting contents; resizing images and tables; finding and replacing text; importing, exporting, and printing Word documents; and using bookmarks and tables of contents. -This Docker image is the predefined Docker container of Syncfusion’s® Word Processor backend. You can deploy it quickly to your infrastructure. +This Docker image is the predefined Docker container of Syncfusion’s® Word Processor back-end. You can deploy it quickly to your infrastructure. Word Processor is a commercial product, and it requires a valid license to use it in a production environment [`(request license or trial key).`](https://help.syncfusion.com/common/essential-studio/licensing/licensing-faq/where-can-i-get-a-license-key) @@ -39,13 +39,13 @@ docker pull syncfusion/word-processor-server version: '3.4' services: - word-processor-server: + word-processor-server: image: syncfusion/word-processor-server:latest environment: #Provide your license key for activation SYNCFUSION_LICENSE_KEY: YOUR_LICENSE_KEY ports: - - "6002:80" + - "6002:80" ``` **Step 3:** In a terminal tab, navigate to the directory where you’ve placed the docker-compose.yml file and execute the following. @@ -54,9 +54,9 @@ services: docker-compose up ``` -Now the Word Processor server Docker instance runs in the localhost with the provided port number `http://localhost:6002`. Open this link in a browser and navigate to the Word Processor Web API control `http://localhost:6002/api/documenteditor`. It returns the default get method response. +Now the Word Processor server Docker instance runs in the localhost with the provided port number `http://localhost:6002`. Open this link in a browser and navigate to the Word Processor Web API control `http://localhost:6002/api/documenteditor`. It returns the default GET method response. -**Step 4:** Append the Docker instance running the URL `(http://localhost:6002/api/documenteditor)` to the service URL in the client-side Word Processor control. For more information about how to get started with the Word Processor control, refer to this [`getting started page.`](../getting-started) +**Step 4:** Append the Docker instance running URL `(http://localhost:6002/api/documenteditor)` to the service URL in the client-side Word Processor control. For more information about how to get started with the Word Processor control, refer to this [`getting started page.`](../getting-started). ## How to configure spell checker dictionaries path in Docker compose file @@ -78,32 +78,32 @@ services: This YAML definition binds the data folder that is available in the Docker compose file directory. -**Step 2:** In the data folder, include the dictionary files (.dic, .aff) and JSON file. The JSON file should contain the language based dictionary file configuration in the following format. +**Step 2:** In the data folder, include the dictionary files (.dic, .aff) and JSON file. The JSON file should contain the language-based dictionary file configuration in the following format. -```yaml - [ - { - "LanguadeID": 1036, - "DictionaryPath": "fr_FR.dic", - "AffixPath": "fr_FR.aff", - "PersonalDictPath": "customDict.dic" - }, - { - "LanguadeID": 1033, - "DictionaryPath": "en_US.dic", - "AffixPath": "en_US.aff", - "PersonalDictPath": "customDict.dic" - } - ] +```json +[ + { + "LanguageID": 1036, + "DictionaryPath": "fr_FR.dic", + "AffixPath": "fr_FR.aff", + "PersonalDictPath": "customDict.dic" + }, + { + "LanguageID": 1033, + "DictionaryPath": "en_US.dic", + "AffixPath": "en_US.aff", + "PersonalDictPath": "customDict.dic" + } +] ``` ->Note: By default, the json file name should be "spellcheck.json". You can also use different file name by mounting the file name to 'SPELLCHECK_JSON_FILENAME' attribute in Docker compose file as below, +N> By default, the JSON file name should be "spellcheck.json". You can also use a different file name by mounting the file name to the 'SPELLCHECK_JSON_FILENAME' attribute in the Docker compose file as below. ```yaml version: '3.4' services: - word-processor-server: + word-processor-server: image: syncfusion/word-processor-server:latest environment: #Provide your license key for activation @@ -111,20 +111,20 @@ services: SPELLCHECK_DICTIONARY_PATH: data SPELLCHECK_JSON_FILENAME: spellcheck1.json volumes: - - ./data:/app/data + - ./data:/app/data ports: - - "6002:80" + - "6002:80" ``` -**Step 3:** For handling the personal dictionary, place an empty .dic file (e.g.,. customDict.dic file) in the data folder. +**Step 3:** For handling the personal dictionary, place an empty .dic file (e.g., `customDict.dic` file) in the data folder. **Step 4:** Provide the configured volume path to the environment variable like in the following in the Docker compose file. ```yaml version: '3.4' services: - word-processor-server: - image: syncfusion/word-processo -server:latest + word-processor-server: + image: syncfusion/word-processor-server:latest environment: #Provide your license key for activation SYNCFUSION_LICENSE_KEY: YOUR_LICENSE_KEY @@ -137,11 +137,11 @@ services: ## How to copy template Word documents to Docker image -You can copy the required template Word documents into docker container while deploying the docker image to server. You can open these Word documents present in the server by passing the document path (name with relative path) to LoadDocument() web API. +You can copy the required template Word documents into the docker container while deploying the docker image to the server. You can open these Word documents present in the server by passing the document path (name with relative path) to the LoadDocument() web API. ->Note: Place the word files in the data folder mentioned in the volumes section(i.e., C:/Docker/Data) of the docker-compose.yml file. All the files present in the folder path (C:/Docker/Data) mentioned in the volumes section of ‘docker-compose.yml’ file will be copied to the respective folder (/app/Data) of docker container. The Word documents copied to docker container can be processed using the 'LoadDocument' web API. +N> Place the word files in the data folder mentioned in the volumes section (e.g., C:/Docker/Data) of the docker-compose.yml file. All the files present in the folder path (C:/Docker/Data) mentioned in the volumes section of the 'docker-compose.yml' file will be copied to the respective folder (/app/Data) of the docker container. The Word documents copied to the docker container can be processed using the 'LoadDocument' web API. -The following code example shows how to use LoadDocument() API in document editor. +The following code example shows how to use the LoadDocument() API in Document Editor. {% tabs %} {% highlight html tabtitle="Composition API (~/src/App.vue)" %} @@ -167,7 +167,7 @@ onMounted(function () { httpRequest.onreadystatechange = function () { if (httpRequest.readyState === 4) { if (httpRequest.status === 200 || httpRequest.status === 304) { - //Open the document in DocumentEditor + //Open the document in Document Editor documenteditor.value.ej2Instances.open(httpRequest.responseText); } } @@ -208,7 +208,7 @@ export default { httpRequest.onreadystatechange = function () { if (httpRequest.readyState === 4) { if (httpRequest.status === 200 || httpRequest.status === 304) { - //Open the document in DocumentEditor + //Open the document in Document Editor this.$refs.documenteditor.ej2Instances.open(httpRequest.responseText); } }