Rails example issues

[sclorg]

Rails example issues

[mfojtik]

@ewolinetz @bparees

[mfojtik]

3. is handled by sticky sessions at router, so ignore it :)

[bparees]

@mfojtik to be clear the default behavior is clientip based routing, but same difference basically.

[ewolinetz]

@mfojtik with 1) we are using admin user and admin password for the db connection currently... do we want to reuse those variables for that or create some new ones?

[mfojtik]

@ewolinetz afaik we use ADMIN_USER just in template:

π ~/go/src/github.com/openshift/rails-ex ack 'ADMIN_USER'
openshift/templates/rails-postgresql.json
334:      "name": "ADMIN_USERNAME",

We should use it for the app instead of 'openshift' and 'secret'.

[ewolinetz]

@mfojtik strange... it looks like that should have been removed. that was remnants of the expression used in the config/database.yaml It has since been replaced with POSTGRESQL_ADMIN_PASSWORD. I would propose that they are instead renamed to something like APPLICATION_USER and APPLICATION_PASSWORD in addition to being added to the container's env. Thoughts?

[mfojtik]

@ewolinetz +1 APPLICATION_USER sounds better... also make it clear that you will have to enter these in order to login to application :-) we should also set them to static values and document it.

[mfojtik]

@ewolinetz good news... 2) is not an issue... i scaled rails to 2 replicas and somehow screw the DB.

[ewolinetz]

@mfojtik hmm, i remember seeing another issue when scaling the app up with it interacting with the db but that's different than what you have pasted above... strange

[ewolinetz]

@mfojtik i think i just came across 2) when testing my PR, it seems that it didn't run db migrate initially...? i'll test your PR and then try to recreate it again after

[bparees]

@ewolinetz I merged @mfojtik 's PR which does migration on deploy now. so 2 should be fixed.

[bparees]

definitely needs more doc/cleanup around what user to use with the app though.

[mfojtik]

@bparees @ewolinetz i think we fixed all issues... I will do some more testing for rails-ex today, but closing this issue.