action-requests-demo.jamey..../config/prod.exs
James Greenwood cc4cc65950
All checks were successful
build / build (push) Successful in 11s
Initial commit: Phoenix LiveView demo for interactive data tables with filtering, sorting, pagination, URL state, and progressive enhancement
Implements a fully-featured action requests table in a single LiveView module using Flop, Ecto, and SQLite. Includes:

- Fuzzy search, status/assignment filters, column sorting, 15-per-page pagination
- Real-time updates, bookmarkable URLs via `handle_params/3`
- JS-disabled fallback with GET forms (no duplicate logic)
- 1,000,000 seeded records, Tailwind + DaisyUI styling, light/dark themes
- Comprehensive README with comparisons to Django+React/Rails+React stacks
- 31 tests covering all scenarios

Tech: Phoenix 1.8+, LiveView, Flop, Ecto, SQLite, Elixir 1.15+
2025-11-17 14:42:00 +00:00

23 lines
825 B
Elixir

import Config
# Note we also include the path to a cache manifest
# containing the digested version of static files. This
# manifest is generated by the `mix assets.deploy` task,
# which you should run after static files are built and
# before starting your production server.
config :action_requests_demo, ActionRequestsDemoWeb.Endpoint,
cache_static_manifest: "priv/static/cache_manifest.json"
# Allow LiveView/WebSocket connections from the deployed host
config :action_requests_demo, ActionRequestsDemoWeb.Endpoint,
check_origin: [
"https://action-requests-demo.jamey.stream",
"//action-requests-demo.jamey.stream"
]
# Do not print debug messages in production
config :logger, level: :info
# Runtime production configuration, including reading
# of environment variables, is done on config/runtime.exs.