Added pattern-pedia-auth component

[TYueksel]

Depends on those two PRs:

• UI
• API

[manuwei]

@TYueksel I realized that it would be good to have this setup in a different docker-compose file - can you add one?

[TYueksel]

Just renamed the existing file to docker-compose.auth.yml

[ghareeb-falazi]

It doesn't seem to me like a good idea that the whole contents of the docker-compose file is copied into a new one... future changes in the original file need to be copied here. Is there a way that the authentication component is declared in a separate file that extends the original file?

[TYueksel]

It doesn't seem to me like a good idea that the whole contents of the docker-compose file is copied into a new one... future changes in the original file need to be copied here. Is there a way that the authentication component is declared in a separate file that extends the original file?

There are three ways how we could start pattern atlas with the authentication component separately from the original version without authentication, candidates and issues:

1. Use 2 docker-compose files (the way it is right now). Depending on which version you want to use, you either run docker-compose.yml or docker-compose.auth.yml.
   • Disadvantage: You already mentioned them.
2. Use 2 docker-compose files where docker-compose.auth.yml only contains the authentication service. Depending on which version you want to use, you either only run docker-compose.yml or both docker-compose files (reference).
   • Advantage: Future changes are only need to be done in one file.
   • Disadvantage: Configuring and starting is a little bit more complex (even more if other components like this might join in the future), since configurations between the files are merged or overridden. The files are merged in the order they’re specified on the command line, which is a little bit error prune in my opinion.
3. Use 1 docker-compose file and introduce profiles to the services. In this case we would only need to include the authentication service to a profile. Services without profiles will always start, while services with profiles will only start if they are specified in command line. Depending on which version you want to use, you either run docker-compose up to run everything without the authentication service or docker-compose --profile auth up to run everything including the authentication service (reference).

I would recommend using the third option, because it seems to me, that this one is fitting best, easily adjustable for the future and less complex than option 2.

[lharzenetter]

LGTM

[mar-be]

JDBC_DATABASE_NAME is a duplicate key