search

FreeUKGen / FreeUKGenealogy

Apache License 2.0
0 stars 0 forks source link

c9.io TEST2 and TEST3 instances #38

Closed ghost closed 5 years ago

ghost commented 5 years ago
  1. Get up to speed on c9.io operations
  2. Implement TEST2 and TEST3 instances
  3. Document workflows
ghost commented 5 years ago

Progress:

Development test instance now available at https://dev-freeukgenealogy-craft-arswright.c9users.io/

ghost commented 5 years ago

Process repeated for https://staging-freeukgenealogy-craft-arswright.c9users.io/ (u: preview / p: preview) and TEST3 instance confirmed working.

@DeniseColbert Now that TEST2 (repository: arswright/FreeUKGenealogy) and TEST3 (repository: FreeUKGen/FreeUKGenealogy) are set up we can perform destructive testing at either instance.

It does not appear as though test2.freeukgenealogy.org.uk or test3.freeukgenealogy.org.uk are set up in forward DNS (instead, we are presently using dev-freeukgenealogy-craft-arswright.c9users.io for TEST2 and staging-freeukgenealogy-craft-arswright.c9users.io for TEST3) - marking this issue closed but please reopen and advise if additional action is required.

DeniseColbert commented 5 years ago

Have you seen this @arswright-alt-uk ?

image

ghost commented 5 years ago

@DeniseColbert I hadn't received this email yet - will await resolution on https://github.com/FreeUKGen/Coordination/issues/1131

PatReynolds commented 5 years ago

@arswright-alt-uk if you have a preferred solution (or advice to avoid something) please do let us know.

ghost commented 5 years ago

@PatReynolds I'm not aware of any limitations which would prevent us from running dev, test, and staging instances of the application on the production AWS instance (though obviously care would need to be taken to ensure isolation between development and production databases).

PatReynolds commented 5 years ago

Thanks, @arswright-alt-uk . @richpomfret may elucidate, but we are trying to separate Test and Production. It may not be so much of an issue for the F U G website.

ghost commented 5 years ago

New issue on task of test server setup at FreeUKGen/Coordination/issues/867

richpomfret commented 5 years ago

Imo, it makes sense to replicate the test2/test3 format we follow for all of our other sites. I am still exploring just how we use Cloud9 (the AWS version - which does use EC2 instances for dev environments). In which case, the workflow in the past has involved setting up workspaces - @Captainkirkdawson or @benwbrum can clarify here.

Captainkirkdawson commented 5 years ago

We want the developer to run in their own workspace not a common one. I see no need to have 2 workspaces such as test2/3. There is no difference in code. Their only difference is that test2 runs under rails as development environment and uses a development database. test3 as a production environment and a production style database (sharded in the case of REG) Any code set can be run as development or production do there is no need for the complexity being proposed.

ghost commented 5 years ago

Added mod_auth (u:test/p:test) access restriction to discourage search engine indexing of test instances.

@richpomfret My understanding (per this comment from Denise) was that we needed a replacement for the discontinued C9.io - if the plan is to continue using the AWS Cloud9 platform for testing, shouldn't these instances be set up under AWS Cloud9? (Either way, I develop locally and would only be using test2 and test3 for acceptance testing w/Denise and staging w/the CMS migration)

ghost commented 5 years ago

@DeniseColbert OK to close if you would please confirm that you are able to access test instances with username test / password test

DeniseColbert commented 5 years ago

Test2 worked fine, test3 just showed me the screen; didn't require login.

ghost commented 5 years ago

@DeniseColbert Ah, I added authentication directives to the http:// virtualhost, not the https://one (worked in testing against http://test3.freeukgenealogy.org.uk/ but obviously not w/SSL).

Please re-test to confirm working at this time - my apologies for the oversight!

DeniseColbert commented 5 years ago

No worries, that fixed it :)

ghost commented 5 years ago

Access confirmed per @DeniseColbert - no further action on issue at this time.