The problem manifests itself as errors in the Eureka server
log (gh-47), but originates in the client because it is sending
requests to /eureka/apps/{NAME}/{ID} with the wrong ID. The
InstanceInfo has an ID that is derived (for preference) from
the EurekaInstanceConfig.dataCenterInfo, so that's the best
way to fix it.

See gh-63, Fixes gh-47

fixes gh-50

fixes gh-53

fixes gh-58

fixes gh-40

fixes gh-57

and how to use it. In particular you can't use it before the
ApplicationContext is past phase=0 of lifecycle startup.

Fixes gh-48

I didn't see a way to do this without dynamic rendering, so
now we have a freemarker dependency (not huge I guess).

Fixes gh-51

Fixes gh-52

Most browsers support <base href="..."> these days and there
was one already in statut.ftl (but not in navbar). Added a test
that asserts the css is loadable as well.

Fixes gh-55

Removed old zuul module.

fixes gh-14

move SpringClientFactory bean creation to RibbonAutoConfiguration where it should have been in the first place.

fixes gh-35

Fixes gh-49

fixes #16

To enable EUreka-first bootstrap.

See gh-42

Fixes gh-42

See gh-42

It works quite well locally actually. I tested with hostnames
127.0.0.1 and 127.0.1.1 and 2 servers running on localhost.

See gh-28

Fixes gh-46

All static content is excluded in the Jersey config, so we can use
/eureka for the prefix to the Eureka API (i.e. /apps etc.)

Fixes gh-44

Unfortunately only properties that have been set show up (unlike
/configprops), but possibly better than nothing. You can see some
in the Eureka server or in the customers sample (once it has
tries to contact the stores service and Ribbon is up and running).

Fixes gh-38