Added Github Actions for testing PRs for Docker Builds (Issue #83)

[Sak1012]

This pull request introduces a new GitHub Actions workflow (docker-pr.yml) to automate the building of Docker images for the eventyay-tickets project. The workflow is triggered whenever a pull request is opened or updated targeting the development or main branches. Additionally, it checks and installs Python dependencies before building the Docker image.

• Tries to solve issue Add Github Actions for testing PRs for Docker Builds #83

Changes Made

• Added a new workflow file docker-pr.yml in the .github/workflows directory.
• Configured the workflow to check and install Python dependencies using the requirements.txt file located in the src directory.
• Built the Docker image using the installed dependencies.
• Ensured that the workflow only runs for pull requests targeting the development or main branches.
• Tested the workflow locally to ensure proper functionality.

ScreenShots

These are screenshots of example tests that were tested with my local fork of eventyay-tickets

Test Getting triggered on a pull-request made to the development branch of my local repository.

Success message of the test while trying to create a PR in-between to local branches aimed at development branch

[marcoag]

@Sak1012 Thanks a lot for the PR, I had a look at commit 19975bb and it looks pretty good. Unfortunately we had to run a hard reset on the development branch due to a messed up merge, would you mind cherry picking the relevant changes and opening a PR against the current development branch?

If you have trouble doing it or you prefer I can do it myself, I just didn't want to steal the authorship of this PR from you ;)

[marcoag]

Please open a new PR against current development branch.

[norbusan]

LGTM, we will see in reality how well it fares.

I would probably fix a certain Python version, the one that is required by ticekts.

Build fails

[norbusan]

This PR fails.
Have you tried a local installation before with the same recipe?
With Python 3.12 being automatically selected, it breaks. Same with 3.11 which I tried.

I fear that the very old dependencies, in particular for psycopg2 will make it difficult to automatize it.

We need osycopg2 builds for the version in the requirements for some version of Python we want to use.

I guess the best way forward is:

• update psycopg2 to 2.9.9 which is the latest available version
• test that eventyay-tickets works with that
• bump the requirements version

and after all that is done, we can have github actions tests.

[norbusan]

Can we use 3.8 here as we do with all other versions and tests?

[Sak1012]

I have updated the Version to "3.8" and the build is successful, please take a look

[mariobehling]

Ok, I am merging this to test.