Romke van Dijk

@jessevz There are some merge conflicts left before we can merge this one. Could you take a look into this one?

@xbenyx Could you have a look at this?

When `HASHTOPOLIS_APIV2_ENABLE` is not set the API will just return a hardcode string, no json or slim errors just: one line: `APIv2 is not enabled, it can be enabled via...

Just status code 200.

Yeah, we fixed this in the dev branches already. You can potentially run the hashtopolis/frontend:dev and hashtopolis/backend:dev containers; note that that code is highly expirimental

Our goal is to merge dev into master next week and create a release in two weeks; but that all depends on our availability and if we run into any...

This one was not fixed, now no error is currently returned: 

So the changes missed the release train :(. But, are in the current dev branch. The code so far is returning a 404 because config.json is not there. This is...

Linking #998 for API implementation

👍 confirmed, the 404 error is fixed. Still waiting for #998.