Reputation
208
Top tag
Next privilege 250 Rep.
View close votes
Badges
1 3 16
Impact
~44k people reached

  • 0 posts edited
  • 2 helpful flags
  • 159 votes cast
Apr
15
awarded  Popular Question
Apr
6
awarded  Popular Question
Jan
19
awarded  Notable Question
Oct
16
awarded  Nice Question
Oct
16
awarded  Yearling
Sep
24
awarded  Autobiographer
Sep
19
awarded  Popular Question
Sep
9
awarded  Curious
Jul
15
comment Serving assets on two different ports
Yes this worked!! thanks! now I understand nginx.conf better!!
Jul
15
accepted Serving assets on two different ports
Jul
15
comment Serving assets on two different ports
here's the app1 config: gist.github.com/tim-peterson/32a67466c7c8d52ceda6 (it's nearly identical to app2's config)
Jul
15
comment Serving assets on two different ports
here's the app2 config: gist.github.com/tim-peterson/ad2c1fae03f850ec7247
Jul
15
comment Serving assets on two different ports
here's the nginx.conf: gist.github.com/tim-peterson/eb180321a079acc21355
Jul
15
comment Serving assets on two different ports
That didn't fix the problem unfortunately. Is this a relative path issue? See my url's above: '/assets/foo.js'
Jul
15
comment Serving assets on two different ports
ok thanks, testing this now...
Jul
15
asked Serving assets on two different ports
May
9
comment No longer can get nginx.conf to respect my redirect rules
sorry I left off the ".com". Thanks for spotting this mistake. I corrected the question. I think this is and Elastic Load Balancer issue. developer24hours.blogspot.com/2013/02/…
May
9
revised No longer can get nginx.conf to respect my redirect rules
added 4 characters in body
May
8
asked No longer can get nginx.conf to respect my redirect rules
Jan
28
awarded  Teacher