Skip to content

armgit / core

Public Imported from GitHub
0

100% open-source IoT Platform - Integrate your devices, add intelligence, build custom apps

Default sandbox e-mail server for MVP

Michal Rutka189ddcd859d0
diff --git a/gitlab-ci/aws-cloudformation.template.arm64.yml b/gitlab-ci/aws-cloudformation.template.arm64.yml
index c38adabaa..2c6b40dad 100644
--- a/gitlab-ci/aws-cloudformation.template.arm64.yml
+++ b/gitlab-ci/aws-cloudformation.template.arm64.yml
@@ -100,8 +100,11 @@ Resources:
sudo pip3 install -U openremote-cli
# Prepare deployment files
cd /home/ubuntu # we need this because on arm docker-compose cannot read /
- wget -nc https://github.com/openremote/openremote/raw/master/profile/deploy-no-build.yml
- wget -nc https://github.com/openremote/openremote/raw/master/profile/demo-no-build.yml
+ # Create volume for deployment (needed for SWARM due to concurency in compose-file)
+ docker volume create openremote_deployment-data
+ docker run --rm -v openremote_deployment-data:/deployment openremote/deployment:latest
+ wget https://github.com/openremote/openremote/raw/master/mvp/mvp-docker-compose.yml
+ docker swarm init
if [ ${HostName} ] && [ ${DomainName} ]
then
echo export DOMAINNAME=${HostName}.${DomainName} >> deploy.sh
@@ -122,10 +125,10 @@ Resources:
echo export [email protected] >> deploy.sh
# Running docker-compose before docker stack deploy has to do with AWS
# problems to fetch letsencrypt CERT in the swarm mode.
- echo 'docker-compose -f demo-basic-no-build.yml -p openremote up -d' >> deploy.sh
- echo sleep 10 >> deploy.sh # give time to fetch CERT from letsencrypt
- echo 'docker-compose -f demo-basic-no-build.yml -p openremote down' >> deploy.sh
- echo openremote-cli deploy -v >> deploy.sh
+ echo 'docker-compose -f mvp-docker-compose.yml -p openremote up -d' >> deploy.sh
+ #echo sleep 10 >> deploy.sh # give time to fetch CERT from letsencrypt
+ #echo 'docker-compose -f demo-basic-no-build.yml -p openremote down' >> deploy.sh
+ #echo openremote-cli deploy -v >> deploy.sh
chmod +x deploy.sh
chown --recursive 1000:1000 *
./deploy.sh
@@ -142,10 +145,6 @@ Resources:
FromPort: '80'
ToPort: '80'
CidrIp: 0.0.0.0/0
- - IpProtocol: tcp
- FromPort: '8081'
- ToPort: '8081'
- CidrIp: 0.0.0.0/0
- IpProtocol: tcp
FromPort: '443'
ToPort: '443'
@@ -153,4 +152,4 @@ Resources:
- IpProtocol: icmp
FromPort: '8'
ToPort: '-1'
- CidrIp: 0.0.0.0/0
+ CidrIp: 0.0.0.0/0
\ No newline at end of file
diff --git a/mvp/mvp-docker-compose.yml b/mvp/mvp-docker-compose.yml
index 54eb0d5f5..2f20306ab 100644
--- a/mvp/mvp-docker-compose.yml
+++ b/mvp/mvp-docker-compose.yml
@@ -138,10 +138,13 @@ services:
# SETUP_WIPE_CLEAN_INSTALL: # Allow override on CLI
# Configure SMTP smart host, to send password reset emails etc.
- SETUP_EMAIL_HOST: email-smtp.eu-west-1.amazonaws.com
- SETUP_EMAIL_USER: ${SETUP_EMAIL_USER:-smtp-user}
- SETUP_EMAIL_PASSWORD: ${SETUP_EMAIL_PASSWORD:-smtp-password}
- SETUP_EMAIL_PORT: ${SETUP_EMAIL_PORT:-25}
+ # We put here sandbox AWS account (allows max 1 msg/s, 200/day and recipient is [email protected])
+ # by doing this we don't have initialization errors and we can see that somebody is using e-mail function
+ # and might be interested in production e-mail server.
+ SETUP_EMAIL_HOST: ${SETUP_EMAIL_HOST:-email-smtp.eu-west-2.amazonaws.com}
+ SETUP_EMAIL_USER: ${SETUP_EMAIL_USER:-AKIAR6UPFQB5OQT6HQ7O}
+ SETUP_EMAIL_PASSWORD: ${SETUP_EMAIL_PASSWORD:-BL+37Uy86pwT6NpM3FyRQkeYu6IQN2m6nc3zgiDI1wYp}
+ SETUP_EMAIL_PORT: ${SETUP_EMAIL_PORT:-587}
SETUP_EMAIL_TLS: 'true'
#SETUP_EMAIL_FROM_KEYCLOAK: '[email protected]'
#SETUP_EMAIL_FROM_DEFAULT: '[email protected]'
diff --git a/profile/demo-no-build.yml b/profile/demo-no-build.yml
deleted file mode 100644
index 9e11903c1..000000000
--- a/profile/demo-no-build.yml
+++ /dev/null
@@ -1,112 +0,0 @@
-# OpenRemote v3
-#
-# By default running this profile installs the stack on https://localhost using a
-# self-signed SSL certificate, with username 'admin' and password 'secret'.
-#
-# Install Docker Community edition (https://docker.com/) on Windows, macOS, or Linux.
-#
-# Start a demo stack in the project root directory with:
-#
-# docker-compose up
-#
-# For full documentation, see deploy.yml
-#
-# Steps to create a permanent installation:
-#
-# 1. DO NOT FORGET TO CHANGE SETUP_ADMIN_PASSWORD!
-#
-# 2. Consider setting a custom DOMAINNAME, LE_EMAIL, and IDENTITY_NETWORK_HOST, see deploy.yml
-#
-# 3. Understand how bind mounts and volume mappings work, see below and read:
-# https://docs.docker.com/engine/admin/volumes/bind-mounts/
-# https://docs.docker.com/engine/admin/volumes/volumes/#choose-the--v-or-mount-flag
-# Survival guide: docker volume ls|rm|prune
-#
-# 4. Execute once:
-#
-# SETUP_WIPE_CLEAN_INSTALL=true \
-# SETUP_ADMIN_PASSWORD=secret \
-# docker-compose up
-#
-# This creates the initial database and optionally imports some examples. Inspect the
-# running installation and ensure it's working. You should now stop the stack and remove
-# all containers. It is important that you recreate the containers and start again WITHOUT
-# the SETUP_WIPE_CLEAN_INSTALL setting! Passwords can be changed in the application.
-#
-# Database schemas will be upgraded to new versions of the services automatically, you do
-# not have to wipe all data to install a new version of OpenRemote.
-#
-# Your extension JAR files should be in the deployment/manager/extensions/ directory.
-#
-version: '2.4'
-
-# If you enable volume mappings in services, you need this. Otherwise, remove the volumes
-volumes:
- proxy-data:
- deployment-data:
- postgresql-data:
-
-services:
-
- # This service will only populate an empty volume on startup and then exit.
- # If the volume already contains data, it exits immediately.
- deployment:
- image: openremote/deployment:${DATE_TAG:-latest}
- volumes:
- - deployment-data:/deployment
-
- # This configuration does not store SSL certificate data and allow changes to the
- # proxy configuration, it is only configured for deployment on localhost. You can
- # map a Docker volume or host directory to access/store proxy configuration files
- # and SSL certificates.
- proxy:
- extends:
- file: deploy-no-build.yml
- service: proxy
- depends_on:
- manager:
- condition: service_healthy
- volumes:
- - proxy-data:/deployment
- # Override the haproxy.cfg with custom file
- # -${MY_PROXY_CONFIG_FILE}:/etc/haproxy/haproxy.cfg
- environment:
- DOMAINNAME: demo.openremote.io
-
- # This configuration uses the manager's deployment-specific data such as map tiles,
- # console application static resources (HTML, JS, CSS), extensions, and other
- # configuration files which were baked into the managers image.
- manager:
- extends:
- file: deploy-no-build.yml
- service: manager
- depends_on:
- keycloak:
- condition: service_healthy
- volumes:
- - deployment-data:/deployment
- - /deployment.local/manager:/deployment.local
- environment:
- MAP_TILES_PATH: '/deployment.local/map/mapdata.mbtiles'
- IDENTITY_NETWORK_HOST: demo.openremote.io
- FIREBASE_CONFIG_FILE: '/fcm.json'
-
- keycloak:
- extends:
- file: deploy-no-build.yml
- service: keycloak
- depends_on:
- postgresql:
- condition: service_healthy
- volumes:
- - deployment-data:/deployment
-
- # This configuration stores postgresql data in a Docker volume. You manage this volume
- # independently from your stack with with 'docker volume ls', 'docker volume rm', etc.
- # Alternatively, you can store postgresql data in a directory on your host.
- postgresql:
- extends:
- file: deploy-no-build.yml
- service: postgresql
- volumes:
- - postgresql-data:/var/lib/postgresql/data