Skip to content
This repository has been archived by the owner on Nov 5, 2024. It is now read-only.

[FEATURE] Web api with headless server #3648

Open
3 tasks done
rougsig opened this issue Oct 25, 2024 · 1 comment
Open
3 tasks done

[FEATURE] Web api with headless server #3648

rougsig opened this issue Oct 25, 2024 · 1 comment
Labels
user request Feature/improvement requested by an user

Comments

@rougsig
Copy link
Contributor

rougsig commented Oct 25, 2024

Please confirm the following:

  • I've checked the current issues for duplicate issues.
  • I've requested a single (only one) feature/change in this issue. It complies with the One Request Per GitHub Issue (ORPGI) rule.
  • My issue is well-defined and describes how it should be implemented from UI/UX perspective.

What do you want to be added or improved?

I propose the integration of an API that interfaces with a headless CMS (Supabase/Directus/etc) to enable content synchronization across multiple devices. This API should facilitate seamless data updates, across multiple devices, ensuring content consistency and accessibility for users whether they are online or offline.

Special column, lock-free impl
We should to develop single repository interface for all remote servers. Than we can implement adaper on client side for that server. Or use generic one and implement adapter on the server side.

Why do you need it?

The app's current offline-only functionality limits its reliability. No easy way to see and analyze/edit information from PC.

How do you imagine it?

API Development/Integration:

  • Develop or integrate an API to interact with a headless CMS. This will facilitate server communication for data retrieval and storage.
  • Add UI to set server url and api keys.
  • Develop an Directus docker template to self-host the instance of the server. Or Supabase template for cloud deploy.

Special column, Why directus?

@rougsig rougsig added the user request Feature/improvement requested by an user label Oct 25, 2024
@ivywallet
Copy link
Collaborator

Thank you @rougsig for raising Issue #3648! 🚀
What's next? Read our Contribution Guidelines 📚.

Tagging @ILIYANGERMANOV for review & approval 👀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
user request Feature/improvement requested by an user
Projects
None yet
Development

No branches or pull requests

2 participants