[PR #3129] [CLOSED] feat: customize supabase auth path #5587

Closed
opened 2026-03-23 22:19:24 +00:00 by mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/AppFlowy-IO/AppFlowy/pull/3129
Author: @LucasXu0
Created: 8/6/2023
Status: Closed

Base: mainHead: custom_supabase_auth_path


📝 Commits (3)

  • e427b1e feat: support build arm64 macOS package on CI
  • b58b38a feat: support build arm64 macOS package on CI
  • e12cdd4 feat: support customizing the supabase auth path

📊 Changes

8 files changed (+197 additions, -20 deletions)

View changed files

📝 .github/workflows/release.yml (+88 -2)
📝 frontend/Makefile.toml (+12 -0)
📝 frontend/appflowy_flutter/lib/startup/tasks/supabase_task.dart (+58 -3)
📝 frontend/appflowy_flutter/macos/Podfile (+25 -12)
📝 frontend/appflowy_flutter/pubspec.lock (+2 -2)
📝 frontend/appflowy_flutter/pubspec.yaml (+2 -0)
📝 frontend/scripts/flutter_release_build/build_universal_package_for_macos.sh (+1 -1)
📝 frontend/scripts/makefile/flutter.toml (+9 -0)

📄 Description

Feature Preview

  • support opening AppFlowy both in develop mode and production mode.

For now, the default supabase auth directory is ApplicationDataStorage + supabase_auth.

Screenshot 2023-08-06 at 15 05 32 Screenshot 2023-08-06 at 15 03 08

PR Checklist

  • My code adheres to the AppFlowy Style Guide
  • I've listed at least one issue that this PR fixes in the description above.
  • I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes.
  • All existing tests are passing.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/AppFlowy-IO/AppFlowy/pull/3129 **Author:** [@LucasXu0](https://github.com/LucasXu0) **Created:** 8/6/2023 **Status:** ❌ Closed **Base:** `main` ← **Head:** `custom_supabase_auth_path` --- ### 📝 Commits (3) - [`e427b1e`](https://github.com/AppFlowy-IO/AppFlowy/commit/e427b1e5bce4da32de27fa3a9e6c35d90719b64d) feat: support build arm64 macOS package on CI - [`b58b38a`](https://github.com/AppFlowy-IO/AppFlowy/commit/b58b38a61596116727608656393ab948c6bd3c55) feat: support build arm64 macOS package on CI - [`e12cdd4`](https://github.com/AppFlowy-IO/AppFlowy/commit/e12cdd425865660d3658e3db8dc14c35ce9da64c) feat: support customizing the supabase auth path ### 📊 Changes **8 files changed** (+197 additions, -20 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/release.yml` (+88 -2) 📝 `frontend/Makefile.toml` (+12 -0) 📝 `frontend/appflowy_flutter/lib/startup/tasks/supabase_task.dart` (+58 -3) 📝 `frontend/appflowy_flutter/macos/Podfile` (+25 -12) 📝 `frontend/appflowy_flutter/pubspec.lock` (+2 -2) 📝 `frontend/appflowy_flutter/pubspec.yaml` (+2 -0) 📝 `frontend/scripts/flutter_release_build/build_universal_package_for_macos.sh` (+1 -1) 📝 `frontend/scripts/makefile/flutter.toml` (+9 -0) </details> ### 📄 Description <!--- Thank you for submitting a pull request to AppFlowy. The team will dedicate their best efforts to reviewing and approving your pull request. If you have any questions about the project or feedback for us, please join our [Discord](https://discord.gg/wdjWUXXhtw). --> <!--- If your pull request adds a new feature, please drag and drop a video into this section to showcase what you've done! If not, you may delete this section. --> ### Feature Preview - support opening AppFlowy both in develop mode and production mode. For now, the default supabase auth directory is `ApplicationDataStorage + supabase_auth`. <img width="536" alt="Screenshot 2023-08-06 at 15 05 32" src="https://github.com/AppFlowy-IO/AppFlowy/assets/11863087/f8c6cfe6-3f7d-4576-b823-c0eb655ddb25"> <img width="737" alt="Screenshot 2023-08-06 at 15 03 08" src="https://github.com/AppFlowy-IO/AppFlowy/assets/11863087/dca1fd2e-6c51-41ff-8fe8-9bc9261d5690"> <!--- List at least one issue here that this PR addresses. If it fixes the issue, please use the [fixes](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests) keyword to close the issue. For example: fixes https://github.com/AppFlowy-IO/AppFlowy/pull/2106 --> --- <!--- Before you mark this PR ready for review, run through this checklist! --> #### PR Checklist - [ ] My code adheres to the [AppFlowy Style Guide](https://appflowy.gitbook.io/docs/essential-documentation/contribute-to-appflowy/software-contributions/submitting-code/style-guides) - [ ] I've listed at least one issue that this PR fixes in the description above. - [ ] I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes. - [ ] All existing tests are passing. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
mirror 2026-03-23 22:19:24 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#5587
No description provided.