You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think removing all storage drivers except the PostgreSQL one would be a good idea.
One major problem when it comes to the implementation of new features that somewhat affect the paste models is that we always have to keep in mind that old data has to be migrateable.
Only the PostgreSQL driver implements auto-migration and maintaining migration logic for every single storage driver would dramatically decrease the development effectivity.
Migrating pastes stored with another driver always include the manual import and export tool which is annoying.
However, we should keep the file storage driver but restrict it to only be accessible when in development mode to not force the developer to set up a fully-fledged PSQL database just to improve some part of the frontend.
Setting up PostgreSQL should not be an issue and I think removing support for other storage options is an acceptable trade-off to achieve a much better development effectivity and flexibility.
The text was updated successfully, but these errors were encountered:
I think I can agree on only supporting PostgreSQL and SQLite as I can write similar migrations for both of them.
SQLite would allow you to run pasty without setting up a dedicated PostgreSQL server, just like with the current file system storage.
lus
linked a pull request
Aug 22, 2022
that will
close
this issue
I think removing all storage drivers except the PostgreSQL one would be a good idea.
One major problem when it comes to the implementation of new features that somewhat affect the paste models is that we always have to keep in mind that old data has to be migrateable.
Only the PostgreSQL driver implements auto-migration and maintaining migration logic for every single storage driver would dramatically decrease the development effectivity.
Migrating pastes stored with another driver always include the manual import and export tool which is annoying.
However, we should keep the file storage driver but restrict it to only be accessible when in development mode to not force the developer to set up a fully-fledged PSQL database just to improve some part of the frontend.
Setting up PostgreSQL should not be an issue and I think removing support for other storage options is an acceptable trade-off to achieve a much better development effectivity and flexibility.
The text was updated successfully, but these errors were encountered: