|
Yes, that would be helpful. We will be looking into improving notification in the near future, so this issue would be good to have
|
|
0
|
0
|
January 20, 2025
|
|
I will create a feature request for this
|
|
0
|
0
|
January 20, 2025
|
|
Guys, is there really no option to remove past notifications?… its annoying that they reappear everytime i open appflowy 🙄
|
|
0
|
1
|
January 20, 2025
|
|
<@845200741751717898> quick question are we still using Tauri for anything?
Saw that in the main AppFlowy repo it got removed but its still in the docs.
https://docs.appflowy.io/docs/documentation/appflowy/from-source/tauri-setup
|
|
0
|
12
|
January 20, 2025
|
|
Not necessarily, it is possible to use Nginx to strip the prefix before passing the request to admin frontend, just like what we did for gotrue/supabase auth service
|
|
0
|
6
|
January 20, 2025
|
|
Though i still need to verify this
|
|
0
|
0
|
January 20, 2025
|
|
We can reuse this issue: https://github.com/AppFlowy-IO/AppFlowy/issues/5380
|
|
0
|
0
|
January 20, 2025
|
|
You can keep using this version and upgrade to the next one when it's released
|
|
0
|
0
|
January 20, 2025
|
|
Ok thank you for your help
|
|
0
|
0
|
January 20, 2025
|
|
No black screen with this version 👍
|
|
0
|
1
|
January 20, 2025
|
|
Thanks for testing! I'll include the fix in the upcoming release
|
|
0
|
0
|
January 20, 2025
|
|
Nice, happy to help
Can I use this version, or need to wait for next release?
|
|
0
|
0
|
January 20, 2025
|
|
Hey, <@220147877522046977>. Would you mind testing the Windows package I DMed you to see if the black screen issue still occurs on your Windows?
|
|
0
|
2
|
January 20, 2025
|
|
Ok I will check
|
|
0
|
0
|
January 20, 2025
|
|
Yes, more details about your needs would be the best. We have included in our near term roadmap
|
|
0
|
0
|
January 18, 2025
|
|
I was sure there was a FR for adding a user field type (to assign a user to a task for example), but I can't find it on github, should I create one?
|
|
0
|
2
|
January 18, 2025
|
|
The web app is insane ! 😄, i will deploy it on selfhosted
|
|
0
|
0
|
January 18, 2025
|
|
Sorry for the delay, here's the issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7139
|
|
0
|
3
|
January 18, 2025
|
|
Can you send me the link for the issue? I am not sure if I found a new one or if its the same
|
|
0
|
1
|
January 17, 2025
|
|
But we realize that this leads to some other bugs, for example, Minio redirect URL env, which shouldn't have used this value
|
|
0
|
6
|
January 17, 2025
|
|
FQDN here is simply used to compute the other required env variable, it is not actually passed to any of the services directly
|
|
0
|
1
|
January 17, 2025
|
|
FQDN here is not the domain for Appflowy web, but AppFlowy Cloud
|
|
0
|
3
|
January 17, 2025
|
|
Originally we set API_EXTERNAL_URL, something like, http://mydomain/gotrue
|
|
0
|
5
|
January 17, 2025
|
|
Should we have a variable for this?
|
|
0
|
0
|
January 17, 2025
|
|
If i have 30 users, i willl not configure them on each computer lol
|
|
0
|
0
|
January 17, 2025
|
|
So, why there is a `FQDN` envronement vairable?
|
|
0
|
0
|
January 17, 2025
|
|
There are also other considerations, such as, there could be users who would prefer to just use something like Vercel to manage AppFlowy Web, in which case the current nginx configuration will be more convenient
|
|
0
|
0
|
January 17, 2025
|
|
The above is still very much in the air right now - we haven't fully investigated the impact, and how much effort will be required for existing self hoster to do the migration
|
|
0
|
1
|
January 17, 2025
|
|
Https://discord.com/channels/903549834160635914/1171707854701461565/1329776326793756722
|
|
0
|
1
|
January 17, 2025
|
|
^^ The discussion on why we have this text field instead of fetching via API
|
|
0
|
0
|
January 17, 2025
|