eclipse-sailing-analytics/sailing-analytics
1
0 Fork 0
mirror of https://github.com/eclipse-sailing-analytics/sailing-analytics.git synced 2026-10-14 16:20:57 +00:00
Code Activity

Merge remote-tracking branch 'origin/master'

Browse Source
This commit is contained in:
Nicolas committed 2014-06-25 17:06:22 +02:00
2 parents 97ca0a6a3d bb83fb7eb8
commit ff60ac8414
1 file changed
+3 -1
Download Patch File Download Diff File Expand all files Collapse all files
wiki/amazon-ec2.md
+3 -1
View File
@@ -267,7 +267,9 @@ Here are the steps to create a load balanced setup:
- Create a master instance holding all data (see http://wiki.sapsailing.com/wiki/amazon-ec2#Setting-up-Master-and-Replica)
- Create `n` instances that are configured to connect to the master server
- Create a load balancer that redirects everything from port 80 to let's say port 8888.
- Create a load balancer that redirects everything from HTTP port 8888 to HTTP port 8888 and leave the other switches and checkboxes on their default value
- As "Ping Port" enter HTTP port 8888 and use /index.html as the "Ping Path." Leave the other values on their defaults again.
- Put the ELB into the "Sailing Analytics App" security group as it will appear in the landscape as a regular sailing analytics application server.
- Associate all your instances
- Connect your domain with the IP of the load balancer. It could be a good idea to use an Elastic IP that always stays the same for the domain and associate it with your load balancer. That way you can also easily switch between a load balancer and a single instance setup.