vapor | A Rails-based application for managing servers in the cloud | Continuous Deployment library

I'm using Vapor to handle http requests. I've implemented a registration and login, as well as other functioning code. On registration, a Bearer Token is generated, so I can return that to or write it into the page I'm about to render.

The page contains two forms, one of which generates a request that requires authorization, so I need to associate that request with the bearer token. How do I do this? Through explicitly setting headers for the form request that will be sent to the server? Via a cookie?

I run a website that handles large files (uploads and downloads). Currently I am transitioning the site from Perfect to Vapor. In Perfect, it is relatively simple to stream a file to users, and then perform some actions AFTER the file is done.

I am trying to do the same thing in Vapor, but I can't seem to figure out how to set a callback when the stream finished, and when it finished, whether it was completely downloaded by the user or there was an interruption.

Is anyone aware of how to do this? Here are some things that I have tried.

This is the basic structure

For the auto-fill password to work on the Apple platforms, I am testing out Apple App Site Association (AASA) Validator in this website. I have added the required json in the Public/.well-known/apple-app-site-association file for the auto-fill password to work on my iOS application.

The result from this test comes back with this error: Your file's 'content-type' header was not found or was not recognized.

Does anyone have ever encounter this issue? It seems that the AASA file is not being downloading into my device.

Note that on iOS 14, AASA files will be delivered via Apple's CDN, which is different from how AASA files are currently downloaded.

Is there something else to do about it on my Vapor 4 project to make things work?

I'm new to Vapor,

I try to pass data from postgres to leaf.

In the routes.swift I have the function to render the leaf template:

I am making a post request using vapor swift client. My code looks like this

I'm running Vapor 4.3 and Leaf with Xcode on my Mac without any issues.

public directory middleware is enabled:

I would like to know if I am using the best practices here as I send the user credentials in a Content-Type: application/json way, without protecting the password. I would like to know if I can protect my route with a middleware and make the user signing up in the safest way possible on my Vapor 4 application.

Can I use Authorization: Basic to sign up a user on my Vapor app ? Is it the normal flow that I am doing here?

This is the way I sign up a user. There is my table with the UserModel, and this is the extension to handle the sign up flow.

I'm carrying this on from this question, since the focus has changed.

I am trying to send string data from a vapor server over a websocket. The client side is where the main question is. This code successfully receives the string, which is expected to be JSON (but not absolutely guaranteed -- out of scope).

Github action deployment fails because of not matching composer-runtime-api ^2.0.0 even though actions/checkout@v2 is used that uses composer v2

laravel.yml: