summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorCorey Hulen <corey@hulen.com>2015-06-22 11:44:06 -0800
committerCorey Hulen <corey@hulen.com>2015-06-22 11:44:06 -0800
commitf6638bb14242adfa307fe0539169df842134fe56 (patch)
tree9950a0377cc7ad15ea7bc27a903035b8afa445ac
parentf2bc8fb41fb34ebaa22d8c1845070b627b585093 (diff)
parent9fcc9fed099480f8065a195afc17283055913cd1 (diff)
downloadchat-f6638bb14242adfa307fe0539169df842134fe56.tar.gz
chat-f6638bb14242adfa307fe0539169df842134fe56.tar.bz2
chat-f6638bb14242adfa307fe0539169df842134fe56.zip
Merge pull request #52 from mattermost/readme
HELIUM - Sections for install instructions
-rw-r--r--README.md62
1 files changed, 35 insertions, 27 deletions
diff --git a/README.md b/README.md
index fa692c59b..e934f3408 100644
--- a/README.md
+++ b/README.md
@@ -76,6 +76,7 @@ You can update to the latest bits by running
`docker pull mattermost/platform:latest`
If you wish to remove mattermost-dev use the following commands
+
1. `docker stop mattermost-dev`
2. `docker rm -v mattermost-dev`
@@ -83,33 +84,40 @@ If you wish to remove mattermost-dev use the following commands
AWS Elastic Beanstalk Setup (Docker)
------------------------------------
-1. From the AWS console select Elastic Beanstalk
-2. Select "Create New Application" from the top right.
-3. Name the application and press next
-4. Select "Create a web server" environment.
-5. If asked, select create and AIM role and instance profile and press next.
-6. For predefined configuration select docker. For environment type select single instance.
-7. For application source, select upload your own and upload Dockerrun.aws.json from docker/Dockerrun.aws.json. Everything else may be left at default.
-8. Select an environment name, this is how you will refer to your environment. Make sure the URL is available then press next.
-9. The options on the additional resources page may be left at default unless you wish to change them. Press Next.
-10. On the configuration details place. Select an instance type of t2.small or larger.
-11. You can set the configuration details as you please but they may be left at their defaults. When you are done press next.
-12. Environment tags my be left blank. Press next.
-13. You will be asked to review your information. Press Launch.
-14. Up near the top of the dashboard you will see a domain of the form \*.elasticbeanstalk.com copy this as you will need it later.
-15. From the AWS console select route 53
-16. From the sidebar select Hosted Zones
-17. Select the domain you want to use or create a new one.
-18. Modify an existing CNAME record set or create a new one with the name * and the value of the domain you copied in step 13.
-19. Save the record set
-20. Return the Elastic Beanstalk from the AWS console.
-21. Select the environment you created.
-22. Select configuration from the sidebar.
-23. Click the gear beside software configuration.
-24. Add an environment property with the name “MATTERMOST\_DOMAIN” and a value of the domain you mapped in route 53. For example if your domain is \*.example.com you would enter example.com not www.example.com.
-25. Select apply.
-26. Return to the dashboard on the sidebar and wait for beanstalk update the environment.
-27. Try it out by entering the domain you mapped into your browser.
+1. Create a new elastic beanstalk docker application using the Dockerrun.aws.json file provided.
+ 1. From the AWS console select Elastic Beanstalk
+ 2. Select "Create New Application" from the top right.
+ 3. Name the application and press next
+ 4. Select "Create a web server" environment.
+ 5. If asked, select create and AIM role and instance profile and press next.
+ 6. For predefined configuration select docker. For environment type select single instance.
+ 7. For application source, select upload your own and upload Dockerrun.aws.json from docker/Dockerrun.aws.json. Everything else may be left at default.
+ 8. Select an environment name, this is how you will refer to your environment. Make sure the URL is available then press next.
+ 9. The options on the additional resources page may be left at default unless you wish to change them. Press Next.
+ 10. On the configuration details place. Select an instance type of t2.small or larger.
+ 11. You can set the configuration details as you please but they may be left at their defaults. When you are done press next.
+ 12. Environment tags my be left blank. Press next.
+ 13. You will be asked to review your information. Press Launch.
+ 14. Up near the top of the dashboard you will see a domain of the form \*.elasticbeanstalk.com copy this as you will need it later.
+
+2. Map a wildcard domain to the new elastic beanstalk application
+ 15. From the AWS console select route 53
+ 16. From the sidebar select Hosted Zones
+ 17. Select the domain you want to use or create a new one.
+ 18. Modify an existing CNAME record set or create a new one with the name * and the value of the domain you copied in step 1.13.
+ 19. Save the record set
+
+3. Set the enviroment variable "MATTERMOST\_DOMAIN" to the domain you mapped above (example.com not www.example.com)
+ 20. Return the Elastic Beanstalk from the AWS console.
+ 21. Select the environment you created.
+ 22. Select configuration from the sidebar.
+ 23. Click the gear beside software configuration.
+ 24. Add an environment property with the name “MATTERMOST\_DOMAIN” and a value of the domain you mapped in route 53. For example if your domain is \*.example.com you would enter example.com not www.example.com.
+ 25. Select apply.
+
+4. Try it out!
+ 26. Return to the dashboard on the sidebar and wait for beanstalk update the environment.
+ 27. Try it out by entering the domain you mapped into your browser.
License
-------