Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server Endpoint management fixes #4

Closed
GavinMendelGleason opened this issue Sep 4, 2019 · 1 comment
Closed

Server Endpoint management fixes #4

GavinMendelGleason opened this issue Sep 4, 2019 · 1 comment

Comments

@GavinMendelGleason
Copy link
Member

Currently there are two places in which it is necessary to specify the server name. One is in the configuration script which creates the initial terminus database. The other is a legacy config/config.pl which allowed some configuration of predicates.

We should be trying to move as much as possible to the terminus database. This means the initial startup script should probably use a configuration file to draw from - perhaps config.pl in order to set defaults. Much better that this information resides in one place than two.

The configuration script also doesn't handle different protocols (https versus http) and just takes the server name. This is obviously wrong. We need to either increase the number of parameters to the script, or draw them from configuration.

We may also need to think about how we deal with slight difference of server. Apache has virtual servers to handle this issue. This is easy enough in swipl, but not actually achieved by the current code.

@GavinMendelGleason
Copy link
Member Author

We are punting on virtual servers for now. The rest should have already been done by @rrooij

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant