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

Revert postgres migration back to sqlite3 #30

Merged
merged 1 commit into from
Feb 4, 2024
Merged

Conversation

munshkr
Copy link
Owner

@munshkr munshkr commented Feb 4, 2024

In retrospect, I think it was a good idea to use SQLite because it is simpler to setup, manage, consumes less resources and it's good enoguh for the requirements of this application.

In retrospect, I think it was a good idea to use SQLite because it is
simpler to setup, manage, consumes less resources and it's good enoguh
for the requirements of this application.
Copy link

gitguardian bot commented Feb 4, 2024

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

@munshkr munshkr merged commit dbe7c3b into main Feb 4, 2024
2 checks passed
@munshkr munshkr deleted the revert-postgres branch February 4, 2024 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant