Description
Followed the PaaS instructions installing on AWS. Used latest version of docker 1.24 instead of 1.4.2 and didn’t add “Storage” … I already had my AWS instance up and running.
The startup scripts didn’t automatically start up , so I started rocketchat manually … and it’s working … I have registered the server etc. However some startup messages worry me… see ******** below
-------------------------------------------------------------- Log …
rocketchat_1 | LocalStore: store created at
rocketchat_1 | LocalStore: store created at
rocketchat_1 | LocalStore: store created at
rocketchat_1 | Setting default file store to GridFS
*************** | Warning: connect.session() MemoryStore is not
rocketchat_1 | designed for a production environment, as it will leak
rocketchat_1 | memory, and will not scale past a single process.
rocketchat_1 | ufs: temp directory created at “/tmp/ufs”
rocketchat_1 | Loaded the Apps Framework and loaded a total of 0 Apps!
rocketchat_1 | Using GridFS for custom sounds storage
rocketchat_1 | Using GridFS for custom emoji storage
rocketchat_1 | Updating process.env.MAIL_URL
rocketchat_1 | ➔ System ➔ startup
rocketchat_1 | ➔ ±-------------------------------------------------------+
rocketchat_1 | ➔ | SERVER RUNNING |
rocketchat_1 | ➔ ±-------------------------------------------------------+
rocketchat_1 | ➔ | |
rocketchat_1 | ➔ | Rocket.Chat Version: 1.1.1 |
rocketchat_1 | ➔ | NodeJS Version: 8.11.4 - x64 |
rocketchat_1 | ➔ | MongoDB Version: 4.0.10 |
rocketchat_1 | ➔ | MongoDB Engine: mmapv1 |
rocketchat_1 | ➔ | Platform: linux |
rocketchat_1 | ➔ | Process Port: 3000 |
rocketchat_1 | ➔ | Site URL: https:// … mydomainname …
rocketchat_1 | ➔ | ReplicaSet OpLog: Enabled |
rocketchat_1 | ➔ | Commit Hash: 80341ed12f |
rocketchat_1 | ➔ | Commit Branch: HEAD
Server Setup Information
- Version of Rocket.Chat Server: 1.1.1
- Operating System: 18.04.1 LTS
- Deployment Method: docker
- Number of Running Instances: 1
- DB Replicaset Oplog: Enabled
- NodeJS Version: 8.11.4 - x64
- MongoDB Version: 4.0.10
- Proxy: nginx
- Firewalls involved: AWS