Deploying HQ
This page describes deploying Lenses HQ via docker.
The HQ docker image can be configured via volume mounts for the configuration file.
The HQ looks for the config.yaml in the current working directory. This is the root directory for Docker.
Running the Docker
docker run --name lenses-hq \
--network panoptes \
-p 8080:8080 \
-v $(pwd)/config.yaml:/config.yaml\
lensting/lenses-hq:6-preview
Prerequisites
The main pre-requirements that has to be fulfilled before Lenses HQ container can be started and those are:
Complete configuration file
In demo purposes and testing the product you can use our community license
license_key_2SFZ0BesCNu6NFv0-EOSIvY22ChSzNWXa5nSds2l4z3y7aBgRPKCVnaeMlS57hHNVboR2kKaQ8Mtv1LFt0MPBBACGhDT5If8PmTraUM5xXLz4MYv
Main configuration file that has to be configured before running docker command is config.yaml.
Sample configuration file is following:
auth:
administrators:
- admin
- admin@company.com
users:
- username: admin
# bcrypt("correcthorsebatterystaple").
password: $2a$10$F66cb6ZhnJjGCZuxlvKP1e84eytTpT1MDJcpBblHaZgsqp1/Aa0LG
sessionDuration: 24h
saml:
enabled: true
baseURL: https://lenses6.company.com
entityID: https://lenses6.company.com
metadata: |
<?xml version="1.0" encoding="UTF-8"?><md:EntityDescriptor
xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata"
</md:IDPSSODescriptor>
</md:EntityDescriptor>
userCreationMode: manual
groupMembershipMode: manual
uiRootURL: /
groupAttributeKey: groups
authnRequestSignature:
enabled: false
http:
address: :8080
accessControlAllowOrigin:
- https://lenses6.company.com
accessControlAllowCredentials: false
secureSessionCookies: false
agents:
address: :10000
database:
host: postgres-postgresql.postgres.svc.cluster.local:5432
username: $(LENSESHQ_PG_USERNAME)
password: $(LENSESHQ_PG_PASSWORD)
schema:
database: lenseshq
TLS: false
license:
key: license_key_
acceptEULA: true
logger:
mode: text
level: debug
metrics:
prometheusAddress: :9090
More about configuration options you can find on the HQ configuration page.
What's next?
After the successful configuration and installation of HQ, the next steps would be: