Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Test http app server doesn't get all the same config as the main one #97

Closed
dmcassel opened this issue May 21, 2013 · 2 comments
Closed
Assignees
Labels

Comments

@dmcassel
Copy link
Collaborator

If you want to add a setting to the main HTTP app server, like the collation, you do it by adding the setting in deploy/ml-config.xml. However, the test app server doesn't get all the config from ml-config.xml, it's made in server_config.rb.

Fix this so that any settings applied to the main app server are also applied to the test app server, except for the port and content database.

Thanks to Steve Brockman for the catch.

@mblakele
Copy link
Contributor

I think you should also consider excluding authentication-method from that list. I might set the main app server to application-level, but still want to use digest for the test server.

It might also be nice to route requests to '/' on the test server to '/test/'.

@ghost ghost assigned dmcassel Jun 7, 2013
dmcassel added a commit that referenced this issue Jun 11, 2013
… server, except the following:

- app name (app-name-test)
- port (test-port)
- content database (test-content-db)
- modules database (test-modules-db if defined, else app-modules-db)
- authentication method (test-authentication-method if defined, else authentication-method)
@dmcassel
Copy link
Collaborator Author

Fixed. I added a test-authentication-method property for mblakele.

dmcassel added a commit that referenced this issue Jun 11, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants