[GH-ISSUE #4340] [FR] self-host support mobile #1938

New issue

Closed

opened 2026-03-23 21:18:22 +00:00 by mirror · 3 comments

mirror commented

2026-03-23 21:18:22 +00:00

Owner

Originally created by @annieappflowy on GitHub (Jan 9, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4340

Originally assigned to: @LucasXu0 on GitHub.

Description

Can we switch the url in the mobile app to self hosted as well? Or is there a workaround in the mean time?

Impact

self-hosting appflowy users

Additional Context

No response

Originally created by @annieappflowy on GitHub (Jan 9, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4340 Originally assigned to: @LucasXu0 on GitHub. ### Description Can we switch the url in the mobile app to self hosted as well? Or is there a workaround in the mean time? ### Impact self-hosting appflowy users ### Additional Context _No response_

mirror

2026-03-23 21:18:22 +00:00

closed this issue
added the
self-hosted
label

mirror commented

2026-03-23 21:18:23 +00:00

Author

Owner

@LucasXu0 commented on GitHub (Jan 9, 2024):

For now, I have disabled the self-hosted entry on the mobile platform with the beta AppFlowy cloud server. The entry will only show if we publish AppFlowy without embedding the beta cloud server.

Is it necessary to display the entry even when the application has been linked to the AppFlowy cloud? In my opinion, it's a little redundant. For internal use, of course, we can still display the entry.

@LucasXu0 commented on GitHub (Jan 9, 2024): For now, I have disabled the self-hosted entry on the mobile platform with the beta AppFlowy cloud server. The entry will only show if we publish AppFlowy without embedding the beta cloud server. Is it necessary to display the entry even when the application has been linked to the AppFlowy cloud? In my opinion, it's a little redundant. For internal use, of course, we can still display the entry.

mirror commented

2026-03-23 21:18:23 +00:00

Author

Owner

@vlbosch commented on GitHub (Jan 10, 2024):

I wouldn't mind two versions. One with the Cloud server you're offering and one version where people can login on their own server (be it Cloud or Supabase). Some VOIP providers for example provide two versions as well. One for their hosting and one for connecting to other servers.

If you prefer to provide only one version , I would default to the AppFlowy server, but provide a button to change to self hosted servers. If left blank, then default to the AppFlowy cloud server again.

Looking forward to a build I can use with my self hosted server. Thanks in advance! :-)

@vlbosch commented on GitHub (Jan 10, 2024): I wouldn't mind two versions. One with the Cloud server you're offering and one version where people can login on their own server (be it Cloud or Supabase). Some VOIP providers for example provide two versions as well. One for their hosting and one for connecting to other servers. If you prefer to provide only one version , I would default to the AppFlowy server, but provide a button to change to self hosted servers. If left blank, then default to the AppFlowy cloud server again. Looking forward to a build I can use with my self hosted server. Thanks in advance! :-)

mirror commented

2026-03-23 21:18:23 +00:00

Author

Owner

@annieappflowy commented on GitHub (Jan 23, 2024):

@vlbosch you can log in randomly and go the cloud settings to connect to your server
In the upcoming mobile version, there will be a self-hosted login option on the startup page

@annieappflowy commented on GitHub (Jan 23, 2024): @vlbosch you can log in randomly and go the cloud settings to connect to your server In the upcoming mobile version, there will be a self-hosted login option on the startup page

mirror referenced this issue

2026-03-23 22:16:53 +00:00

[PR #1938] [MERGED] relicense appflowy editor #5028

mirror referenced this issue

2026-03-23 22:16:55 +00:00

[PR #1944] [MERGED] feat(appflowy_editor): double underscore to bold text for relicensing #5034