User Tools
support:scottypro_architecture
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| support:scottypro_architecture [2018/09/03 17:41] – adsilva | support:scottypro_architecture [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== ScottyPro Ticketer Environment | ||
| + | |||
| + | Author: Avi D' Silva | ||
| + | |||
| + | The current ScottyPro Ticketer runs on an AWS instance, and it was being pointed to using an Iframe. | ||
| + | |||
| + | This entry documents all the changes that were done to move away from the Iframe approach and use the DNS directly. This can also be referred when configuring a new instance with ScottyPro-Ticketer. | ||
| + | |||
| + | The Ticketer instance itself runs on ": | ||
| + | |||
| + | **Install Nginx as a proxy** (sudo apt-get install nginx) | ||
| + | |||
| + | You will find the configuration in / | ||
| + | |||
| + | Now we have to configure nginx to handle the following use cases: | ||
| + | |||
| + | < | ||
| + | 1. Proxy traffic from Port 80 to Port 8083 | ||
| + | |||
| + | 2. Forward all http:// | ||
| + | |||
| + | 3. Redirect all base URL requests to Ticketer App (Ex: http:// | ||
| + | |||
| + | 4. Edge case where Ticketer adds an extra slash " | ||
| + | |||
| + | 5. Edge case where Ticketer adds an extra slash on logout " | ||
| + | </ | ||
| + | |||
| + | First we create a file "/ | ||
| + | This will basically convert any www traffic to non-www | ||
| + | |||
| + | < | ||
| + | server { | ||
| + | server_name www.scottypro.com; | ||
| + | return 301 $scheme:// | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | |||
| + | Next, we create/edit the file "/ | ||
| + | The rules are written to take care of rest of the above use cases. | ||
| + | |||
| + | < | ||
| + | server { | ||
| + | # | ||
| + | # | ||
| + | |||
| + | root / | ||
| + | index index.html index.htm; | ||
| + | |||
| + | # Make site accessible from http:// | ||
| + | server_name scottypro.com; | ||
| + | |||
| + | merge_slashes off; | ||
| + | rewrite ^(.*? | ||
| + | location /Ticketer { | ||
| + | |||
| + | proxy_pass http:// | ||
| + | |||
| + | } | ||
| + | location / { | ||
| + | rewrite ^/(.*)$ http:// | ||
| + | } | ||
| + | |||
| + | location // { | ||
| + | rewrite ^/(.*)$ http:// | ||
| + | } | ||
| + | |||
| + | } | ||
| + | </ | ||
| + | |||
| + | The last thing that remains would be point the A record of scottypro.com (from godaddy.com) to point to the right IP address | ||
| + | |||
| + | Also, add a CNAME record for " | ||