Update Docker access info and installation instructions

Author: Sorita Heng

modules/ROOT/partials/docker/hyperlinking-service/hyperlinking-service-installation.adoc

@@ -1,17 +1,15 @@
 [[installation]]
 == Installation
 
-[NOTE]
-Valid credentials (username and password) are **required** in order to retrieve On-Premises services images from our Docker Registry.
-link:https://www.tiny.cloud/contact/[Contact {companyname} Support] to request credentials.
+include::partial$misc/admon-docker-access.adoc[]
 
 === Retrieve Docker Image
 
 . Login into the {companyname} Cloud Docker Registry: 
 +
 [source, sh, subs="attributes+"]
 ----
-docker login -u [username] -p [password] registry.containers.tiny.cloud
+docker login -u tiny -p [access-token] registry.containers.tiny.cloud
 ----
 
 . Pull the Docker Image from the Docker registry:
@@ -23,6 +21,9 @@ docker pull registry.containers.tiny.cloud/hyperlinking-tiny:<VERSION>
 +
 Replace `<VERSION>` with `latest` or the specific version number.
 
++
+include::partial$misc/admon-available-docker-images.adoc[]
+
 === Specify Configurations 
 
 After completing the previous steps, run the Docker container from the pulled image: 
@@ -56,39 +57,65 @@ If set up correctly, the logs should display output similar to the following:
 
 Running this command will generate a log warning about `allowed-origins` not being configured. This is expected, as it will be set up in the next step.
 
-The {productname} server-side components require a configuration file to function correctly. By convention, this file is named `application.conf`. For more information, refer to link:https://www.tiny.cloud/docs/tinymce/latest/configure-required-services/[Required configuration for the server-side components]. 
+The {productname} server-side components require a configuration file to function correctly. By convention, this file is named `application.conf`. For more information, refer to link:https://www.tiny.cloud/docs/tinymce/latest/configure-required-services/[Required configuration for the server-side components^]. 
 
 This configuration file requires at least the following information:
 
 * allowed-origins - Specifies the domains allowed to communicate with server-side editor features. This is **mandatory** for all server-side components.
 
-The following settings for the premium server-side components are optional and will apply to all services that make outgoing HTTP/HTTPS requests using the configuration file.
+The following settings for the premium server-side components are _optional_ and will apply to all services that make outgoing HTTP/HTTPS requests using the configuration file.
 
-* link:https://www.tiny.cloud/docs/tinymce/latest/configure-common-settings-services/#proxy[proxy configuration]
-* link:https://www.tiny.cloud/docs/tinymce/latest/configure-common-settings-services/#http[http configuration]
+* link:https://www.tiny.cloud/docs/tinymce/latest/configure-common-settings-services/#proxy[proxy configuration^]
+* link:https://www.tiny.cloud/docs/tinymce/latest/configure-common-settings-services/#http[http configuration^]
 
 The following settings for the Hyperlinking premium server-side component are _optional_:
 
-* link:https://www.tiny.cloud/docs/tinymce/latest/configure-hyperlink-service/#link-checking[link-checking configuration]
-* link:https://www.tiny.cloud/docs/tinymce/latest/configure-hyperlink-service/#cache[cache configuration]
+* link:https://www.tiny.cloud/docs/tinymce/latest/configure-hyperlink-service/#link-checking[link-checking configuration^]
+* link:https://www.tiny.cloud/docs/tinymce/latest/configure-hyperlink-service/#cache[cache configuration^]
 
-The {mediaembedplugin} service allows the use of a custom link:https://www.tiny.cloud/docs/tinymce/latest/mediaembed-server-config/#use-your-own-iframely-account[Iframely] account, configured link:https://www.tiny.cloud/docs/tinymce/latest/mediaembed-server-config/#configure-a-custom-endpoint[oEmbed] endpoints, or a combination of both. If a URL lacks an Iframely or oEmbed configuration, the service generates a summary card.
+The {mediaembedplugin} service allows the use of a custom link:https://www.tiny.cloud/docs/tinymce/latest/mediaembed-server-config/#use-your-own-iframely-account[Iframely^] account, configured link:https://www.tiny.cloud/docs/tinymce/latest/mediaembed-server-config/#configure-a-custom-endpoint[oEmbed^] endpoints, or a combination of both. If a URL lacks an Iframely or oEmbed configuration, the service generates a summary card.
 
 [TIP]
 A summary card is an embeddable snippet of code created based on the available metadata and content detected at the URL. This ensures that even if no predefined embedding method is configured, the service can still provide a structured and visually consistent media representation.
 
 When media is inserted into content, the service follows this sequence:
 
-. Check if the URL matches any custom link:https://www.tiny.cloud/docs/tinymce/latest/mediaembed-server-config/#configure-a-custom-endpoint[oEmbed] configuration. If that fails,
-. If link:https://www.tiny.cloud/docs/tinymce/latest/mediaembed-server-config/#use-your-own-iframely-account[Iframely] is configured, query the Iframely API. If Iframely is not configured,
+. Check if the URL matches any custom link:https://www.tiny.cloud/docs/tinymce/latest/mediaembed-server-config/#configure-a-custom-endpoint[oEmbed^] configuration. If that fails,
+. If link:https://www.tiny.cloud/docs/tinymce/latest/mediaembed-server-config/#use-your-own-iframely-account[Iframely^] is configured, query the Iframely API. If Iframely is not configured,
 . Create a summary card.
 
-The following settings for the Enhanced Media Embed service are optional:
+The following settings for the Enhanced Media Embed service are _optional_:
+
+* link:https://www.tiny.cloud/docs/tinymce/latest/mediaembed-server-config/#use-your-own-iframely-account[Iframely account configuration^]
+* link:https://www.tiny.cloud/docs/tinymce/latest/mediaembed-server-config/#configure-a-custom-endpoint[oEmbed customs configuration^]
+
+=== Run the Docker Container
+
+The Docker container can also be run with `docker compose`. In this example, the following directory structure is assumed:
+
+[source,sh]
+----
+image-proxy-service/
+├── application.conf
+└── docker-compose.yaml 
+----
+
+Here is an example of the application.conf file with the basic configurations:
 
-* link:https://www.tiny.cloud/docs/tinymce/latest/mediaembed-server-config/#use-your-own-iframely-account[Iframely account configuration]
-* link:https://www.tiny.cloud/docs/tinymce/latest/mediaembed-server-config/#configure-a-custom-endpoint[oEmbed customs configuration]
+[source,conf]
+----
+ephox {
+
+  allowed-origins {
+    origins = [
+      "<http://example.com>",
+      "<http://good.com> ",
+      "*.my.company.org"
+    ]
+  }
 
-=== Launch the Docker Container
+}
+----
 
 Once the application configuration file is ready, proceed with the Docker Compose setup to configure and run the service.
 
@@ -107,7 +134,7 @@ services:
     init: true
     volumes:
       - type: bind
-        source: <PATH_TO_APPLICATION_CONF_FILE_IN_HOST_MACHINE>
+        source: ./application.conf #change this to the path on your local machine 
         target: /ephox-hyperlinking/ephox-hyperlinking-docker-env.conf 
         read_only: true
 ----
@@ -212,13 +239,15 @@ If an error occurs,  the expected message is: `{ "message": "The supplied authen
 Before deploying, it is recommended to test this service within the {productname} editor itself.
 
 +
-To do this, configure the link:https://www.tiny.cloud/docs/tinymce/latest/linkchecker/[{linkcheckerplugin}] and link:https://www.tiny.cloud/docs/tinymce/latest/introduction-to-mediaembed/[{mediaembedplugin}] features in the editor and call them via `tinymce.init`. If running locally on the default port `19100`, use the following settings:
+To do this, configure the link:https://www.tiny.cloud/docs/tinymce/latest/linkchecker/[{linkcheckerplugin}^] and link:https://www.tiny.cloud/docs/tinymce/latest/introduction-to-mediaembed/[{mediaembedplugin}^] features in the editor and call them via `tinymce.init`. If running locally on the default port `19100`, use the following settings:
 
 +
 [source, js]
 ----
 tinymce.init({
-  …,
+  selector: 'textarea', // change this value according to your HTML
+  plugins: 'code image link linkchecker autolink code',
+  toolbar: 'image link code',
   linkchecker_service_url: "http://localhost:19100",
   mediaembed_service_url: "http://localhost:19100"
 });

modules/ROOT/partials/docker/hyperlinking-service/hyperlinking-service-overview.adoc

@@ -1,10 +1,10 @@
 [[overview]]
 == Overview
 
-The On-Premises version of the link:https://www.tiny.cloud/tinymce/features/link-checker/[{linkcheckerplugin}] and link:https://www.tiny.cloud/tinymce/features/enhanced-media-embed/[{mediaembedplugin}] is an application that can be installed and run on the customer’s in-house servers and computing infrastructure, including a private cloud.
+The On-Premises version of the link:https://www.tiny.cloud/tinymce/features/link-checker/[{linkcheckerplugin}^] and link:https://www.tiny.cloud/tinymce/features/enhanced-media-embed/[{mediaembedplugin}^] is an application that can be installed and run on the customer’s in-house servers and computing infrastructure, including a private cloud.
 
 The only requirement to run these services On-Premises is a container runtime or orchestration tool e.g. Docker, Kubernetes, Podman. 
 
-To get started, contact link:https://www.tiny.cloud/contact/[{companyname} Support] to enable the service. A username and a password will be provided to access the {companyname} Cloud Docker registry and pull the Docker image. 
+A valid access token is required to access the Tiny Cloud Docker registry and pull the Docker image. Contact link:https://www.tiny.cloud/contact/[{companyname} Support^] to request the access token. 
 
 include::partial$misc/admon-dont-push-docker-images.adoc[]

modules/ROOT/partials/docker/hyperlinking-service/hyperlinking-service-requirements.adoc

@@ -1,8 +1,8 @@
 [[requirements]]
 == Requirements
 
-* The link:https://docs.docker.com/engine/docker-overview/[Docker Engine] is installed and running.
+* The link:https://docs.docker.com/engine/docker-overview/[Docker Engine^] is installed and running.
 * The user has Administrative or Root user access to run the Docker commands.
 * The user is either:
-** Using a Linux, Unix or macOS operating system.
+** Using a Unix-like operating system, such as Linux or macOS.
 ** Using Windows and has access to unix command line tools using link:https://gitforwindows.org/[Git for Windows], link:https://www.cygwin.com/[Cygwin], or the link:https://docs.microsoft.com/en-us/windows/wsl/install-win10[Windows Subsystem for Linux].

modules/ROOT/partials/misc/admon-available-docker-images.adoc

@@ -0,0 +1,4 @@
+[NOTE]
+====
+Currently, the Docker images are only supported on x86-64 (also known as AMD64) architecture processors.
+====

modules/ROOT/partials/misc/admon-docker-access.adoc

@@ -0,0 +1,5 @@
+[IMPORTANT]
+====
+A valid access token is **required** in order to retrieve On-Premises services images from {companyname} Cloud Docker Registry.
+link:https://www.tiny.cloud/contact/[Contact {companyname} Support^] to request the access token.
+====