No description
The contact detail page used to gather every enrichment source in one parallel_hydrate/2 bundle and await all five tasks before updating any assigns, so users watched the whole right-hand column flash in at the speed of the slowest query (usually hrrr_profiles_for_path against a 42M-row table). Each source now runs in its own start_async task: :weather, :solar, :hrrr_path, :terrain, :iemre. Matching handle_async/3 clauses assign the slot and call refresh_computed/1, which rebuilds elevation_profile + propagation_analysis + data_sources from whatever's currently in assigns. Sections appear independently as their data arrives, and the existing PubSub handlers (:hrrr_ready, :weather_ready, :terrain_ready, :solar_ready) still pick up later backfill completions the same way they did before. |
||
|---|---|---|
| .forgejo/workflows | ||
| .github | ||
| assets | ||
| bin | ||
| config | ||
| docs | ||
| k8s | ||
| lib | ||
| lib_ml | ||
| notebooks | ||
| priv | ||
| rel | ||
| test | ||
| vendor | ||
| .credo.exs | ||
| .dockerignore | ||
| .formatter.exs | ||
| .gitignore | ||
| .tool-versions | ||
| AGENTS.md | ||
| algo.md | ||
| app.json | ||
| CLAUDE.md | ||
| Dockerfile | ||
| elevation.md | ||
| mix.exs | ||
| mix.lock | ||
| prediction.md | ||
| README.md | ||
| tail_logs.sh | ||
| updates.md | ||
Microwaveprop
To start your Phoenix server:
- Run
mix setupto install and setup dependencies - Start Phoenix endpoint with
mix phx.serveror inside IEx withiex -S mix phx.server
Now you can visit localhost:4000 from your browser.
Ready to run in production? Please check our deployment guides.
Learn more
- Official website: https://www.phoenixframework.org/
- Guides: https://hexdocs.pm/phoenix/overview.html
- Docs: https://hexdocs.pm/phoenix
- Forum: https://elixirforum.com/c/phoenix-forum
- Source: https://github.com/phoenixframework/phoenix