Feature/avatar upload

[Schnoop]

#8

[frank9999]

What is your opinion about storing the avatar as base64encoded string in the database? I'm using multi-server deployments, so persisting user uploads in 1 directory on 1 server will cause issues. Several deployment tools also create a new checkout in a separate directory, which will cause the avatars to break. I can work around these issues by making the avatar upload directory a shared NFS share or use a shared object store... Storing the image in the database seems like the easiest solution, but it may cause performance issues and increase database disk usage/load. @Schnoop

[Schnoop]

Yeah - that would be a good option. If the database should get in trouble at some point in the future it should not be a problem to move the images back to files and think about other deployment options. Maybe a S3 storage is another option to store the user generated images.

[Schnoop]

Changed implementation to store image in database.

[frank9999]

Thanks for this merge request! I left some review notes :)

[codecov-commenter]

Codecov Report

Merging #166 (8ece4f4) into master (fb3b777) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

@@             Coverage Diff             @@
##             master    #166      +/-   ##
===========================================
- Coverage      0.08%   0.08%   -0.01%     
- Complexity     1831    1845      +14     
===========================================
  Files           179     181       +2     
  Lines          6140    6220      +80     
===========================================
  Hits              5       5              
- Misses         6135    6215      +80     

Files Changed	Coverage Δ
src/Controller/Game/UserController.php	0.00% <0.00%> (ø)
src/Entity/User.php	0.00% <0.00%> (ø)
src/Form/UploadAvatarType.php	0.00% <0.00%> (ø)
src/Twig/Base64EncodeExtension.php	0.00% <0.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more