vapor
Here are 614 public repositories matching this topic...
-
Updated
Jan 28, 2022 - Swift
-
Updated
Jan 19, 2022 - Swift
-
Updated
Feb 17, 2022 - Ruby
-
Updated
Feb 12, 2022 - Swift
-
Updated
Oct 10, 2018 - Swift
-
Updated
May 24, 2018 - Swift
-
Updated
Feb 17, 2022 - Swift
-
Updated
Apr 17, 2020 - Swift
-
Updated
Feb 2, 2022 - Swift
-
Updated
Jan 3, 2022 - Swift
-
Updated
Feb 20, 2022 - Swift
I wonder whether it would be possible (good?) to display whether or not a package exclusively uses a binaryTarget or not?
What I mean by this is that there are some Swift packages (example) who's sole purpose are to (re)distribute and make available precompiled xcframeworks to SPM. In these scenarios, there is no source code.
-
Updated
Oct 26, 2021 - Swift
Currently built for Leaf 3, we should add support for Leaf 4
-
Updated
Sep 6, 2021 - Swift
-
Updated
Nov 8, 2018
-
Updated
May 25, 2020 - Swift
-
Updated
Oct 6, 2021 - Swift
I just did a clean install of the vapor toolbox 18.2.2 via homebrew per the Vapor Install Toolbox docs.
brew install vapor
vapor --version
# note: no Package.resolved file was found.
# framework: not found
# toolbox: 18.2.2Note the vapor --version output shown above.
The _"note: no Package.resolved fil
-
Updated
Jan 22, 2022 - Swift
The way we test Vapor as on onward package doesn't work when the PR is from a fork because it tries to check out a revision that doesn't exist. The main Vapor package checks out both the package and forward provider and uses them both so we should copy that
Event list under the http://www.swifttube.co/events should be sorted by "startDate" of the events. Newest event should be listed at the top of the list.
Improve this page
Add a description, image, and links to the vapor topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the vapor topic, visit your repo's landing page and select "manage topics."
When checking a request's
remoteAddress, it's usually the address from which NIO received the request. While that's technically correct, Vapor servers are often hosted behind a reverse-proxy such as nginx. Therefore the original peer's address is often lost. To resolve this, it's not uncommon to set the original peer's address in a header such asX-Forwarded-For.**Describe the solution you