mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 04:46:56 +00:00
[GH-ISSUE #17] [FR] Server sync #6
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @maticrivo on GitHub (Nov 16, 2021).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/17
1~3 main use cases of the proposed feature
Are there plans to have a server one can self-host for syncing files between multiple devices (computers, cellphones, tablets...)?
Alternatively it can be a good option to let the users decide where to store the sqlite database (dropbox, icloud, google drive, etc...)
what types of users can benefit from using your proposed feature
Every user that uses more then 1 device
Additional context
Nothing to add besides this is a great project and it looks great!
@markosole commented on GitHub (Nov 16, 2021):
You may have few options:
Depends of complexity and requirements.
@annieappflowy commented on GitHub (Nov 17, 2021):
Thanks a lot for your inputs. End-to-end encryption sync is sitting on our roadmap. This is something that users with more than one device would need. Your alternative plan sounds promising. I'm wondering where you'd like to store? Is there any data security concern?
Annie
@emengweb commented on GitHub (Nov 18, 2021):
self-host and share with peoole like website :D
@bgervan commented on GitHub (Nov 21, 2021):
I am working on a flutter + hive (can be other DB if it allow to define base class) + crdt + django channels backend package.
Would it be something Appflowy is interested to use? If they implement offline working with that, my package can sync with django backend real time. For one user with multiple device it already works (need to clean the code etc). For multiple user I need to improve it. Of course the django app can be self hosted
@jjeejj commented on GitHub (Feb 17, 2023):
Minio , S3 Or other object storage
@remram44 commented on GitHub (Feb 21, 2023):
Duplicate of https://github.com/AppFlowy-IO/AppFlowy/discussions/540
@annieappflowy commented on GitHub (Feb 27, 2023):
https://github.com/AppFlowy-IO/AppFlowy/issues/602
@iBobik commented on GitHub (Mar 27, 2023):
Some ideas, what do you think?
Would be nice (and cheap) to symmetrically encrypt per file and allow user to share by links.
There could be multiple kind of keys - owner, edit and view. Owner can manage them, generate multiple links with different keys etc. Owner keys could maybe be asymmetric public keys, edit key just random string.
By default owner file keys are stored in user account and view keys in parent folder (in a link to the child file?). User can get share link like: https://share.appflowy.io/FILE_ID#view=FILE_KEY&edit=EDIT_KEY.
On the server there will be dump CDN with SPA. It will get file by its ID from S3-like storage, decrypt by view key in hash and render. So viewing files will be cheap.
For saving and colaboration there will have to be some backend which will check edit and owner keys. Also it can enforce billing.
For sake of freedom there could be not only super simple to use official paid cloud, but also option to store plain markdown files anywhere (local, Dropbox, Drive, iCloud, …).
@annieappflowy commented on GitHub (Mar 28, 2023):
Thanks, @iBobik for your input. I'm learning new things from you!
What benefits would you gain from assigning different keys for different permissions compared to other alternative ways of managing permissions?
@iBobik commented on GitHub (Mar 28, 2023):
Tell me about some specific alternative and I will compare it 😉
But generally usual solutions does not care about privacy and want to motivate more people to create accounts or at least generate leads (collect contacts).
Also my proposal is cheaper to operate. (At least view only sharing.)
@iBobik commented on GitHub (Mar 28, 2023):
Also that view only sharing could be very simple to implement.
@xezzon commented on GitHub (Jul 7, 2023):
Will WebDAV be supported?
@almereyda commented on GitHub (Nov 24, 2023):
Is there a chance that this is now implemented with AppFlowy-IO/AppFlowy-Cloud?
@annieappflowy commented on GitHub (Dec 24, 2023):
We now support self-hosting AppFlowy: https://docs.appflowy.io/docs/guides/appflowy/self-hosting-appflowy