Kitura | A Swift web framework and HTTP server | HTTP library

FTP works like the following: You setup a TCP connection to the FTP server. Over that socket you can send commands, and the server will reply over that same socket. You can use the port command :

You can extend String to give you this functionality (or extract it).

I was able to update and enhance my dockerfile this is now running smoothly and also can be used for CI and CD tasks.

Seems there was a simple approach on that issue... I could use the DateFormatter()

Turns out I had to also include the dependencies into the .target of the Package.swift:

I believe that once your client has completed sign-in, you will have a GIDGoogleUser that provides access to an ID token (JWT) that you can supply to your server. Your server can then validate the token (that it was issued by Google) and extract the user's identity.

See: https://developers.google.com/identity/sign-in/ios/backend-auth

You may be able to use the Kitura-CredentialsJWT middleware to decode the token. Note that as of writing, the plugin only supports Codable routes, but there is an open pull request that adds support for 'raw' routing (using the Kitura-Credentials plugin mechanism).

Update: Kitura-CredentialsJWT support has now been released in tag 1.0.0.

The problem here is that the ibmcom/swift-ubuntu:5.0.2 image is built on top of Ubuntu 14.04. The version of libmysqlclient-dev supplied with 14.04 does not include the pkg-config information that allows the Swift compiler to find the headers without help.

There are two solutions to this problem:

1: You could add -Xcc -I/usr/include/mysql/ arguments to the swift build command. Either:

• replace the command you are executing in the build container with swift build -Xcc -I/usr/include/mysql/, or
• if you'd like to keep using the tools-utils.sh script, you can create a file in your project called .swift-build-linux which contains a single line: swift build -Xcc -I/usr/include/mysql/ - this will be picked up by the tools-utils.sh script when it runs the build.

2: You can replace your base images with FROM swift:5.0.2 (for the build image) and FROM swift:5.0.2-slim (for the run image) - these are the official Swift-maintained images which are based on Ubuntu 18.04, and as of the Swift 5.0.2 release, provide a 'slim' image similar to ibmcom's 'runtime' image.

• Note that these images do not bundle the libssl-dev or libcurl4-openssl-dev dependencies, so you will need to include those in your Dockerfile-tools.

Vapor and Kitura are both build on Apples Swift-NIO.
So you could technicaly go with that as well but you would have to build alot of functionality by yourself that frameworks like vapor and kitura bring, to make you life easier.

Unfortunately, this is not yet possible with Kitura's Codable routes - as you identified, only a trailing :id is supported.

Being able to move the single :id parameter elsewhere within the path might be possible in a relatively small patch. Supporting multiple path parameters would be significantly more complex: Codable routing would need to call your route handler with the right number of (individually typed) parameters. Perhaps there's a half-way house where we could support an array of path parameters (all of a single type).

If you'd like to raise an issue against Kitura and elaborate on your use cases, we could discuss possible solutions and whether they could reduce the need to fall back to 'traditional' routing.