Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NoMongo: Create Central MinIO Client Configuration for talawa-admin #3316

Open
yugal07 opened this issue Feb 28, 2025 · 3 comments
Open

NoMongo: Create Central MinIO Client Configuration for talawa-admin #3316

yugal07 opened this issue Feb 28, 2025 · 3 comments
Labels
documentation Improvements or additions to documentation duplicate This issue or pull request already exists feature request no-issue-activity No issue activity unapproved Unapproved for Pull Request

Comments

@yugal07
Copy link

yugal07 commented Feb 28, 2025

Is your feature request related to a problem? Please describe.

Currently, there is no centralized MinIO client file in the frontend of the application. This creates several challenges:

Contributors need to implement their own MinIO configuration, leading to inconsistencies
The transition from base64 to MinIO storage is fragmented across different parts of the codebase
Duplicate configuration code is likely to emerge as different contributors implement similar solutions
Potential for inconsistent implementation patterns across the application

Describe the solution you'd like

Create a central MinIO client configuration file that can be imported and used throughout the frontend application. This file should:

1.Provide a consistent API for interacting with MinIO storage
2.Handle common operations like uploading, retrieving, and deleting files
3.Include proper error handling and logging
4.Be well-documented to ensure all contributors can use it effectively

Describe alternatives you've considered

Letting each contributor implement their own MinIO client as needed
Creating multiple client files for different types of assets (images, documents, etc.)
Using a third-party library to handle MinIO interactions

Approach to be followed (optional)

Create a new utility file in an appropriate location in the frontend codebase
Implement core functions for common MinIO operations:

1.File upload with proper mime-type detection
2.File retrieval with URL generation
3.File deletion
4.Error handling for all operations

Add documentation with usage examples
Create basic tests to ensure functionality
Update relevant documentation to inform contributors about the new centralized client

Additional context
This task should be completed before other contributors begin working on individual file migration tasks from base64 to MinIO. Once this central configuration is in place, other tasks can use this implementation rather than creating their own.
Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship

PalisadoesFoundation/talawa#359

Copy link

Congratulations on making your first Issue! 🎊 If you haven't already, check out our Contributing Guidelines and Issue Reporting Guidelines to ensure that you are following our guidelines for contributing and making issues.

@github-actions github-actions bot added documentation Improvements or additions to documentation duplicate This issue or pull request already exists unapproved Unapproved for Pull Request labels Feb 28, 2025
@yugal07
Copy link
Author

yugal07 commented Feb 28, 2025

This needs to be opened in talawa-admin. I apologise for inconvenience

@yugal07 yugal07 closed this as completed Feb 28, 2025
@github-project-automation github-project-automation bot moved this from Backlog to Done in NoMongo: Talawa-API Feb 28, 2025
@palisadoes palisadoes reopened this Mar 1, 2025
@github-project-automation github-project-automation bot moved this from Done to Backlog in NoMongo: Talawa-API Mar 1, 2025
Copy link

github-actions bot commented Mar 9, 2025

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

@github-actions github-actions bot added the no-issue-activity No issue activity label Mar 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation duplicate This issue or pull request already exists feature request no-issue-activity No issue activity unapproved Unapproved for Pull Request
Projects
Status: Backlog
Development

No branches or pull requests

2 participants