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. |
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.
...
| Code Block |
|---|
CREATE SERVICE tabmove_service
IN COMPUTE POOL tabmove_container_compute_pool
FROM SPECIFICATION $$
spec:
containers:
- name: tabmove-lite
image: europefmniqai-west1biztory-dockerpartner.registry.pkg.dev/biztory-works/tabmovesnowflakecomputing.com/sbx_timothyvermeiren/tabmove_container_schema/tabmove_container_repository/tabmove-lite:latest
env:
POSTGRES_HOST: "tabmove_db"
POSTGRES_PORT: "5432"
POSTGRES_DB: "tabmove_self_service"
POSTGRES_USER: "tabmove_self_service"
POSTGRES_PASSWORD: "EXwyWyafsHbRLDy2MUj8sCCKoNasdfgpN"
POSTGRES_SSL_MODE: "disable"
CRYPTOLENS_BIZTORY_ACCESS_TOKEN: "WyI4NzcyMTU2MCIsIk1BVk9VNTd4MTluRklFb29LMVhud3lDeWhjUm50L2w3N0tmdVB6cUQiXQ=="
CRYPTOLENS_BIZTORY_RSA_PUBLIC_KEY: "<RSAKeyValue><Modulus>yjnQ01qKzfwGx11KImlT/a8nQyyKmxIzoPX2e+LN88GWkxz3QKR8/YQZrKWwVzn7mkFhX1QKq29SOiHMk/nE9kmdz/ibuumnqLVJYpaYaw0GRjCeYYl80keXMDzILd2lPZLq3tDtrbdKb42YZ8XlvoR/pdpNDMCBXEkUErdtMZyKV2pPIYUjxR96/Cza8xutVUMYEDTNPqJAJxZbw4S1kdS0tkWgcBRqNSmtVj/BpazpPw38CiwtyTRAmPMLdEXzBUIZkVQ1+aSiQLn++AJqd92wR+Yp1P340/JmohjokwODbnl/uQll8fIDQ3xlX3JHdrgY1QWTgOexCb9zmdgvhw==</Modulus><Exponent>AQAB</Exponent></RSAKeyValue>"
CRYPTOLENS_PRODUCT_CODE: "25970"
CRYPTOLENS_MAX_OVERDRAFT: "1"
CRYPTOLENS_FLOATINGTIME_INTERVAL_SECONDS: "600"
- name: tabmove-db
image: fmniqai-biztory-partner.registry.snowflakecomputing.com/sbx_timothyvermeiren/tabmove_container_schema/tabmove_container_repository/postgres:16
env:
PGDATA: /var/lib/postgresql/data/pgdata/
POSTGRES_HOST: "tabmove-db"
POSTGRES_PORT: "5432"
POSTGRES_DB: "tabmove_self_service"
POSTGRES_USER: "tabmove_self_service"
POSTGRES_PASSWORD: "EXwyWyafsHbRLDy2MUj8sCCKoNasdfgpN"
POSTGRES_SSL_MODE: "disable"
volumeMounts:
- name: postgres-data
mountPath: /var/lib/postgresql/data/pgdata
endpoints:
- name: tabmove-lite
port: 80518501
public: true
protocol: HTTPS
volumes:
- name: postgres-data
source: local
$$
MIN_INSTANCES=1
MAX_INSTANCES=1
;
GRANT USAGE ON SERVICE tabmove_service TO ROLE tabmove_container_role; |
...
The ingress_url is the URL we can use to access the TabMove service.
If necessary, we can access the service’s logs (instance ID 0, container name tabmove_lite, tail 10 lines):
| Code Block |
|---|
SELECT SYSTEM$GET_SERVICE_LOGS('tabmove_service', '0', 'tabmove-lite', 10); |
AWS Elastic Container Service (ECS)
...