Use /etc/hosts aliases instead of $DBHOST and other

[NateBrady23]

I noticed that TFB-client TFB-database and TFB-server were already being set up in the /etc/hosts file during vagrant bootstrapping. I've updated the travis setup to do the same. Before something like this gets merged in, a note in the Installation Guide for those not using vagrant is needed.

Ideally, we would no longer need to use $DBHOST and other environment variables for IP addresses. We would also no longer need to use sed in setup files to replace IPs. I've edited a few frameworks here as a proof of concept, but also, the suite uses benchmark.cfg.example if a benchmark.cfg doesn't exist. So for the sake of this travis run, $DBHOST=TFB-database.

[msmith-techempower]

There was once, long ago, an implementation similar to this; we removed it because some frameworks could not resolve names for reasons we could not explain. Hopefully, this is no longer the case....

[NateBrady23]

If it is the case, those frameworks can still do the sed stuff they're doing now and pull in the ip from the /etc/hosts file.

[msmith-techempower]

I see this being done in travis and vagrant, but I don't see this setup happening in the general case (like our production code): you should plan on adding that in.

[NateBrady23]

This would be part of the setup. So it would be something done manually (see the linked installation guide) or did you have something else in mind?

[NateBrady23]

@msmith-techempower Here is the corresponding documentation: https://github.com/TechEmpower/TFB-Documentation/pull/58/files

All of the modified tests pass. We can leave $DBHOST and other environment variables available for now but push future tests and updates toward TFB-database, TFB-client, TFB-server.

If this is good for you, we can merge this in and I can update a lot of the others.

[volyrique]

This is wrong: The URL has nothing to do with the database (note that it is used as a parameter for curl); it is just the location at which the HTTP server is temporarily accessible while gathering the profiling data.

[NateBrady23]

@volyrique Thanks. Going through some of the setups, to test this change. At a quick glance I misread the port as 5432 and associated it with postgres.