Skip to content

tracking issue: axum migration #1900

Closed
Closed
@syphar

Description

@syphar

Current design idea:

  • axum is the main entrypoint for requests
  • when the route is already migrated to axum, we use it,
  • as an axum fallback we call the old iron server for the rest

details

  • database / storage access will stay sync for now, via spawn_blocking (which is the recommended way)
  • template engine can stay the same
  • preferably we don't have to change tests so it's easier to see if behaviour changed.

handler migration status

  • sitemap::sitemapindex_handler
  • sitemap::sitemap_handler
  • sitemap::about_builds_handler
  • statics::static_handler
  • rustdoc::static_asset_handler
  • storage_change_detection
  • build_details::build_details_handler
  • builds::build_list_handler
  • crate_details::crate_details_handler
  • features::build_features_handler
  • metrics::metrics_handler
  • releases::activity_handler
  • releases::build_queue_handler
  • releases::home_page
  • releases::owner_handler
  • releases::recent_releases_handler
  • releases::releases_by_stars_handler
  • releases::releases_failures_by_stars_handler
  • releases::releases_feed_handler
  • releases::releases_recent_failures_handler
  • releases::search_handler
  • rustdoc::badge_handler
  • rustdoc::download_handler
  • rustdoc::rustdoc_html_server_handler
  • rustdoc::rustdoc_redirector_handler
  • rustdoc::target_redirect_handler
  • sitemap::about_handler
  • source::source_browser_handler

links

issues resolved when finished:

issues that we can work on when this is finished:

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions