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

SQLite support as back-end FlowFuse DB #3779

Open
zackwasli opened this issue Apr 25, 2024 · 1 comment
Open

SQLite support as back-end FlowFuse DB #3779

zackwasli opened this issue Apr 25, 2024 · 1 comment
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do

Comments

@zackwasli
Copy link
Contributor

zackwasli commented Apr 25, 2024

Description

Today we support PostgreSQL as the default back-end database for FlowFuse. We should expand this support to include SQLite as an option.

Which customers would this be available to

Enterprise Tier Only (EE)

Requested by:

https://app-eu1.hubspot.com/contacts/26586079/record/0-2/10135626714

@zackwasli zackwasli added feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do labels Apr 25, 2024
@knolleary
Copy link
Member

Our code already supports both SQLite and Postgres. What we would need to know is what install type they are using - docker or k8s?

Given sqlite is based on access to a 'local' file, I'm not sure it makes sense in a k8s install. In a docker install - it would need a persistent volume to be mounted to the right bit of the docker setup. Unless I'm missing something, that would fairly simple to do. But the question is why do they want a different database technology when its an entirely internally managed component ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do
Projects
Status: No status
Development

No branches or pull requests

2 participants