feature(shuttle): adapt shuttle implementation to new server structure
This commit is contained in:
parent
cf0f140ba3
commit
5b69d5bfbe
1 changed files with 2 additions and 2 deletions
|
|
@ -4,7 +4,7 @@ use crate::relay::server::download_success;
|
|||
use crate::relay::server::upload_info;
|
||||
use crate::relay::server::ws_handler;
|
||||
use axum::{
|
||||
routing::{get, post},
|
||||
routing::{get, post, put},
|
||||
Router,
|
||||
};
|
||||
use axum_client_ip::SecureClientIpSource;
|
||||
|
|
@ -23,7 +23,7 @@ async fn axum() -> ShuttleAxum {
|
|||
// Set up the application routes.
|
||||
let app = Router::new()
|
||||
.route("/ws", get(ws_handler))
|
||||
.route("/upload", post(upload_info))
|
||||
.route("/upload", put(upload_info))
|
||||
.route("/download/:name", get(download_info))
|
||||
.route("/download_success/:name", post(download_success))
|
||||
.with_state(appstate)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue