This repository was archived by the owner on Mar 27, 2026. It is now read-only.
Feature: Support mariadb and MinIO#1
Merged
rafaeljusto merged 5 commits intomainfrom Nov 21, 2025
Merged
Conversation
added 5 commits
November 19, 2025 09:33
Provides instructions for setting up MariaDB and MinIO for local development and testing. Includes configuration details and example commands.
…pported in mariadb)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Applying changes from attendee-labs#518 .
At Teamwork most of our stack (especially in our development environment) uses minio for our blob storage and mariadb for our data store. I've provided options here to run attendee with either aws credentials or minio (which shares the same API interface as aws s3), as well as postgres or mariadb/mysql for the database.
I ended up having to split out some of the migrations (and change the order as constraints were defined before schema) where constraint support was not available in mariadb.
I have run docker-compose up for both postgres as well as mariadb support, ensured migrations ran from scratch in both systems. Everything is running for me in development as expected with both database systems.
I have tested this on MacOS.