## 🍰 Pullrequest
This will migrate our assets to an objectstorage via S3.
Before this PR is rolled out, the S3 credentials need to be configured in the respective infrastructure repository. The migration is implemented in a backend migration, i.e. I expect the `initContainer` to take a little longer but I hope then it's going to be fine. If any errors occcur, the migration should be repeatable, since the disk volume is still there.
### Issues
The backend having direct access on disk.
### Todo
- [ ] Configure backend environment variables in every infrastructure repo
- [ ] Remove kubernetes uploads volume in a future PR
Commits:
* refactor: follow @ulfgebhardt
Here: https://github.com/Ocelot-Social-Community/Ocelot-Social/pull/8545#pullrequestreview-2846163417
I don't know why the PR didn't include these changes already, I believe I made a mistake during rebase and lost the relevant commits.
* refactor: use typescript assertions
I found it a better way to react to this comment: https://github.com/Ocelot-Social-Community/Ocelot-Social/pull/8545/files#r2092766596
* add S3 credentials
* refactor: easier to remember credentials
It's for local development only
* give init container necessary file access
* fix: wrong upload location on production
* refactor: follow @ulfgebhardt's review
See: https://github.com/Ocelot-Social-Community/Ocelot-Social/pull/8545#pullrequestreview-2881626504
* shout comments
* fix notifications
* Remove whitespace for empty category sections
* Overhaul post actions
* Adjust spacing
* Allow fine-grained size control for icons and circle buttons via css variables; adjust comments layout
* Adjust spacing
* Add test for ActionButton (WIP)
* Rename import
* Remove text and add count bubble
* Use filled icons to indicate active states
* Adjust sizes and orientation
* Remove unused properties, add test
* Fix ObserveButton test
* Fix ShoutButton test
* fix tests
* Adapt styles
* Adjust style for larger numbers
* Remove unused icon
* Fix test structure
* Remove unused class names
---------
Co-authored-by: Maximilian Harz <maxharz@gmail.com>
* feat(backend): pin more than one post
* add postPinnedCount query, better names for env variable
* add store and mixin for pinned posts counts
* test pinned post store
* context menu for pin posts
* fix typos
* unpin posts is always possible
* feat(backend): pin public group posts
* allow posts in public groups to be pinned by admins
---------
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
* feat(backend): pin more than one post
* add postPinnedCount query, better names for env variable
* add store and mixin for pinned posts counts
* test pinned post store
* context menu for pin posts
* fix typos
* unpin posts is always possible
---------
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
* after authentification, query the categories if active and store them
* get categories from store
* use category store to get categories
* get categories from store
* mock store to have access to categories
* to get rid of the active categories config variable in the frontend, the Category query returns an empty array when categories are not active
* remove CATEGORIES_ACTIVE from .env
* should return string to avoid warnings in console
* replace all env calls for categories active by getter from store
* use categoriesActive getter
* ignore order of returned categories
* mixin to get the category infos from the store, to ensure, that the quey has been called
* fix misspelling
---------
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
* - added case for tablet
* - optimized HeaderMenu for desktop and mobile
- fixed Logo
* - refixed Logo (missing changes)
---------
Co-authored-by: Sebastian Stein <sebastian@codepassion.de>
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
* autoselect badges when rewarding and the suer still have free slots
* improve semantics
---------
Co-authored-by: Hendrik-cpu <62690517+Hendrik-cpu@users.noreply.github.com>
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
I think we can merge this already. The S3 client dependency is outdated
and since the code is behind a feature flag it doesn't get executed. Why
not merge it then?
* feat(backend): add support line to emails
* - fixed snapshots
---------
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
Co-authored-by: Sebastian Stein <sebastian@codepassion.de>
* - optimized header
- added possibility of extra mobile logo
* - changed behavior of NotificationMenu link get directly open for mobile
* - moved notification links to the top of the menu
* - optimized chat view for mobile
* - added logo branding structure
* - added logo branding structure
* - fixed chat height
* - fixed paddings for internal pages
* Fix linting
* Fix linting
---------
Co-authored-by: Sebastian Stein <sebastian@codepassion.de>
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
* define ids and slugs in categories, check for existing ids, only seed the new ids
* seed categories respecting existing categories
---------
Co-authored-by: Ulf Gebhardt <ulf.gebhardt@webcraft-media.de>
* refactor(backend): types for global config
I saw merge conflicts in these files for #8463 so let's get some parts of this PR into `master` already.
I believe this fixes a small bug. They guard clause didn't ensure that all of REDIS_ configurations were set.
* remove old email mechanism
* refactor(backend: react to @ulfgebhardt's review
See: https://github.com/Ocelot-Social-Community/Ocelot-Social/pull/8485#pullrequestreview-2813528327
* build(backend): optional commit
@ulfgebhardt this is how I tested the configurations. We don't need to include this commit but I wouldn't expect to send out real emails from a `docker-compose` setup.
---------
Co-authored-by: Moriz Wahl <moriz.wahl@gmx.de>
