Docker and license-Files

Hello,

the readme of "TeamSite-LiveSite-Docker-Automation-16_3-v3.0.tar" suggests to put license files into the appropriate folders, before doing the docker-compose.

We want to try building TeamSite/LiveSite-Docker-images, based on TS16.3.
We have one question regarding the license files.
What about the hostnames within them?

When firing up a Docker-container, the hostname is random by default:
[user@1a0fa461f5f1 ~]$ hostname
1a0fa461f5f1

How to deal with the License-file? It has the final hostname and domain included and cannot be changed afterwards...

Thu Sep 02 09:28:12 EDT 2017

DOMAIN=mydomain
HOSTNAME=myhostname
KEY=fiowejhfoiwehofhwefhweiofhweiofhwfhwioehio
DATADEPLOY=true
SERVERTYPE=OpenDeploy Development Server
PRODUCT=OD
PLATFORM=Linux
EXPIRES=NoLimits
BASESERVER=true

Thank you for any input in advance.

Kind regards
Heinz Werner

Find more posts tagged with

Comments

HeinzWerner

Hello, can anyone share something regarding this topic?

nipper

I have see some licenses generated for a domain only:

Wed Apr 18 16:19:08 EDT 2018

KEY=ABC123...
DATADEPLOY=true
BASESERVER=false
DOMAIN=myco.com
PRODUCT=OD
EXPIRES=NoLimits
SERVERTYPE=OpenDeploy Development Server
PLATFORM=Linux

That was an 8.1 generated license. I am not certain if the still are that way. I have a mix of with and without.

The only other way is to use a generic name, which is a violation of the license agreement and to have permission before hand. We have done that.

Note, What I suggested would work for runtime servers (OD and LS), not TeamSite servers as the hostname is determined differently.

nipper

I will be interested in how you deal with the DB in an autoscaling mode (for LS). I have a couple ideas how to make LSCS start up, with the content pre-loaded if the load balancer takes the instance down. LSDS is easier that way.