server-side-swift
Here are 486 public repositories matching this topic...
-
Updated
Jul 24, 2021 - Swift
Context and Description
The READMEs and any example code in all projects should be updated to reflect the move from the IBM-Swift organization to the Kitura organization.
If anyone wants to take on all or part of this, please comment here so other's know what you're working on and submit PR's. :-)
Thanks!
-
Updated
May 22, 2022 - Swift
-
Updated
Apr 13, 2022 - Swift
-
Updated
Mar 26, 2020 - Swift
-
Updated
Apr 7, 2019 - Swift
-
Updated
May 13, 2022 - Swift
-
Updated
Jan 24, 2022 - Swift
-
Updated
May 18, 2022 - Swift
-
Updated
Apr 28, 2022 - Ruby
-
Updated
Oct 25, 2018 - Swift
-
Updated
May 22, 2022 - Swift
-
Updated
Feb 10, 2022 - Swift
-
Updated
Mar 29, 2021 - Swift
-
Updated
Oct 10, 2018 - Swift
-
Updated
May 24, 2018 - Swift
-
Updated
Jan 21, 2020 - HTML
-
Updated
May 13, 2022 - Swift
See #165 results
-
Updated
May 16, 2022 - Swift
-
Updated
Apr 17, 2020 - Swift
-
Updated
May 21, 2022 - Swift
-
Updated
May 20, 2022 - Swift
-
Updated
Apr 23, 2022 - Swift
-
Updated
May 15, 2022 - Swift
We should create a GH action that runs whenever a PR is merged to create an issue for translating the documentation issues in that PR. The issue body should contain a link to the PR so we can link them up. This ensures that the translations don't get out of sync.
Even better if we can add a later to the PR to say no-doc-update
required so it doesn't create issues with that label, for instance
-
Updated
Sep 6, 2021 - Swift
-
Updated
Nov 8, 2018
Improve this page
Add a description, image, and links to the server-side-swift topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the server-side-swift 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