Versions Compared

Old Version 4

changes.mady.by.user Timothy Vermeiren

Saved on

compared with

New Version 5

changes.mady.by.user Timothy Vermeiren

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

TabMove Lite is offered as a solution that you can deploy on your own infrastructure in a number of ways. From the simplest to the most advanced, these are:

Method

Difficulty

Remarks

From a marketplace (AWS Marketplace, Salesforce AppExchange)

Easiest

This will become the recommended approach, but is not available yet.

As a container image

Moderate

This is the currently recommended approach. In the future, this will be a decent alternative in case specific requirements can’t be met with the marketplace approach.

As an executable

Advanced

On-demand only, for exceptional use-cases.

Review the information below to learn more about each deployment method.

...

If you want to run TabMove Lite as a container on your own infrastructure (e.g. Docker), you can follow the steps below. The example assumes a local Docker installation for demonstration purposes, but most concepts can be applied e.g. on AWS ECS, GCP, or other infrastructure.

Docker Native

  1. Download the TabMove Lite docker-compose file (docker-compose.yml). Make note of where you save this file, or place it in a dedicated folder.

  2. On your command prompt, navigate to the location where you saved the file and run the service using:
    docker compose up
    The TabMove Lite service will be made available on port 8080.

  3. Access the app:

    1. If you can connect to your Docker host directly and using http, you can use your browser to reach http://your-docker-host:8080/

    2. Alternatively, using a service like Serveo may make it more convenient to access TabMove Lite. Example command to run on your Docker host VM:
      ssh -R 80:localhost:8080 serveo.net
      Serveo will provide you with a unique URL you can access TabMove at for as long as the SSH connection is maintained.

    3. Otherwise, consider using whichever services of infrastructure you have available to make the application available through HTTPS, e.g.:

      1. A reverse proxy

      2. AWS Cloudfront (?)

      3. …

AWS Elastic Container Service (ECS)

Warning

These instructions are untested as of yet, and are here purely for future completion.

  1. Ensure you have the Amazon ECS CLI installed.

  2. Ensure you have your AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_SESSION_TOKEN available to you. Work with your AWS administrator to obtain these if necessary.

  3. Configure your local AWS ECS CLI profile with the following command, substituting profile_name with your desired profile name, and $AWS_ACCESS_KEY_ID, $AWS_SECRET_ACCESS_KEY, and AWS_SESSION_TOKEN environment variables with your AWS credentials.

    ecs-cli configure profile --profile-name profile_name --access-key $AWS_ACCESS_KEY_ID --secret-key $AWS_SECRET_ACCESS_KEY --session-token AWS_SESSION_TOKEN

  4. In your browser, sign in to your AWS Console and access the AWS ECS service (purely to review the assets being created).

  5. Create a new, empty cluster for TabMove:
    ecs-cli up --region eu-central-1 --cluster tabmove --empty

  6. Download the TabMove Lite docker-compose file (docker-compose.yml). Make note of where you save this file, or place it in a dedicated folder.

  7. Bring up the services defined in docker-compose.yml in the AWS ECS cluster:
    ecs-cli compose up

  8. That will fail.