Add base URL to configuration file

[CasperWA]

Makes it possible to set the base URL from the config file. Should otherwise use the base URL gotten from parsing the requested URL (which may be "wrong" if run as a proxy).

[codecov]

Codecov Report

Merging #135 into master will increase coverage by 0.18%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #135      +/-   ##
==========================================
+ Coverage   85.79%   85.98%   +0.18%     
==========================================
  Files          39       39              
  Lines        1830     1826       -4     
==========================================
  Hits         1570     1570              
+ Misses        260      256       -4

Flag	Coverage Δ
#unittests	85.98% <100%> (+0.18%)	⬆️

Impacted Files	Coverage Δ
optimade/server/routers/utils.py	83.73% <100%> (+0.26%)	⬆️
optimade/server/config.py	93.13% <100%> (+3.41%)	⬆️
optimade/server/routers/info.py	96.29% <100%> (-0.14%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f719b14...8d9a6c3. Read the comment docs.

[ltalirz]

thanks @CasperWA !

Besides the comments I have two more questions:

• I tried out your PR since I wanted to check what value the base URL takes if it is parsed from the request. This showed me that I actually don't know where this base URL is actually returned by the API. Can you give an example?
• I think the config.ini file should be at the top level of the repo. Since it is a configuration file, it should not be considered part of the code

[ltalirz]

Oh, so you get the base URL from the request?

I wonder - would that solve the problem of having to specify the base URL?

[CasperWA]

No.
The else value is what used to be up to now, and is giving false information if run in a docker (it will provide you with something like http://localhost:3585 or whatever the port is).

[CasperWA]

I tried out your PR since I wanted to check what value the base URL takes if it is parsed from the request. This showed me that I actually don't know where this base URL is actually returned by the API. Can you give an example?

Sure.
The easiest is to go to the structures endpoint and set a "low" page_limit, e.g., 5.
Then you will see the result of the base URL under the links.next.

I think the config.ini file should be at the top level of the repo. Since it is a configuration file, it should not be considered part of the code

Yeah - it's not a bad idea to combine this PR with fixing #134.
We can use the same implementation/way to find the config file as is used to find the server.cfg file now, i.e., look in the cwd.

[ltalirz]

The easiest is to go to the structures endpoint and set a "low" page_limit, e.g., 5.
Then you will see the result of the base URL under the links.next.

thanks, I tried setting it to 50 but I still see next: null in the json output

[ltalirz]

thanks @CasperWA !