Create project for the API about website HOT 7 CLOSED

The api will be in another project in separate container.

The downside is more initial work for maintaining the network connections.

IMO its ok

from website.

We should choose if we will use REST or GraphQL.

Best syntax ever. :)

This will help with the mobile app integration.

Also we can go to SPA.

My vote goes to graphQL

Same.

from website.

@angelk I've made some testing in #200.

However if the database + the GraphQL backend will be on a separate project, how the connection between the projects will be implemented? As a new virtual host in the apache configuration?

from website.

yes, new virtual host.
For example we may have gaphql hostname for the project.
In the beginning both graphql and website will be connected to the database from the website project.
Later the database will be moved to the graphQL project and database support will be dropped from the website project

from website.

@angelk Another question. The project will be in a separate container or as another project in the current?
I really like the idea separate container for each project. The downside is more initial work for maintaining the network connections.

from website.

Here are some issues:

Should we create separate endpoint for the track downloads (.gpx)
Should we have separate project or endpoint for images uploads?
Same for images serving

from website.

https://github.com/trackhub/api

from website.