Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NOT ISSUE] - Suggestions #35

Open
kuatroka opened this issue Nov 25, 2024 · 1 comment
Open

[NOT ISSUE] - Suggestions #35

kuatroka opened this issue Nov 25, 2024 · 1 comment

Comments

@kuatroka
Copy link

kuatroka commented Nov 25, 2024

Hi, I've listened to your suggestion on the Elixir Mentor podcast and here are my suggestions:

  1. You could make this project as a template on how to integrate a modern and fast non-ecto DB with Phoenix/Liveview.
  2. Focus on how to make a generally fast analytics and data driven Liveview webapp.
  3. Add more details on how to integrate Charts, tables and shadcn/ui.
  4. Explain how to use shadcn/ui in your app and how to add other components and how tweak tailwind themes that come with it by default.
  5. Focus on performance of the app and try different charting libraries (chart.js, Apache eCharts, uPlot, etc)
  6. Show how to deal with duckdb and tables with SSR/backend based non-ecto pagination, sorting, filtering, search/autocomplete.
  7. Maybe venture into other JS integration areas like live_svelte.

Thanks for the tool!

@Exadra37
Copy link

I am not fan of using the DuckDB database, unless the way the app talks with it it's similar to PostgreSQL and not like SQLITE, otherwise it can bring the BEAM VM down in the event of a DuckDB crash.

I would suggest to write docs on how to use a separated PostgreSQL instance for the analytics. I can contribute with a docker integration for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants