Swiftpack.co - Package - p4vlos/Server-Side-Swift-with-Kitura

Scaffolded Swift Kitura server application


Table of Contents


This scaffolded application provides a starting point for creating Swift applications running on Kitura.


Project contents

This application has been generated with the following capabilities and services:

Embedded metrics dashboard

This application uses the SwiftMetrics package to gather application and system metrics.

These metrics can be viewed in an embedded dashboard on /swiftmetrics-dash. The dashboard displays various system and application metrics, including CPU, memory usage, HTTP response metrics and more.

Docker files

The application includes the following files for Docker support:

  • .dockerignore
  • Dockerfile
  • Dockerfile-tools

The .dockerignore file contains the files/directories that should not be included in the built docker image. By default this file contains the Dockerfile and Dockerfile-tools. It can be modified as required.

The Dockerfile defines the specification of the default docker image for running the application. This image can be used to run the application.

The Dockerfile-tools is a docker specification file similar to the Dockerfile, except it includes the tools required for compiling the application. This image can be used to compile the application.

Details on how to build the docker images, compile and run the application within the docker image can be found in the Run section below.

Bluemix cloud deployment

Your application has a set of Bluemix cloud deployment configuration files defined to support deploying your application to Bluemix:

  • manifest.yml
  • .bluemix/toolchain.yml
  • .bluemix/pipeline.yml

The manifest.yml defines options which are passed to the Cloud Foundry cf push command during application deployment.

IBM Bluemix DevOps service provides toolchains as a set of tool integrations that support development, deployment, and operations tasks inside Bluemix. The "Create Toolchain" button creates a DevOps toolchain and acts as a single-click deploy to Bluemix including provisioning all required services.


Your application configuration information is stored in the config.json in the project root directory. This file is in the .gitignore to prevent sensitive information from being stored in git.

The connection information for any configured services, such as username, password and hostname, is stored in this file.

The application uses the CloudConfiguration package to read the connection and configuration information from the environment and this file.

If the application is running locally, it can connect to Bluemix services using unbound credentials read from this file. If you need to create unbound credentials you can do so from the Bluemix web console (example), or using the CloudFoundry CLI cf create-service-key command.

When you push your application to Bluemix, these values are no longer used, instead Bluemix automatically connects to bound services using environment variables.


To build and run the application:

  1. swift build
  2. .build/debug/EmojiJournalServer

NOTE: On macOS you will need to add options to the swift build command: swift build -Xlinker -lc++


To build the two docker images, run the following commands from the root directory of the project:

  • docker build -t myapp-run .
  • docker build -t myapp-build -f Dockerfile-tools . You may customize the names of these images by specifying a different value after the -t option.

To compile the application using the tools docker image, run:

  • docker run -v $PWD:/root/project -w /root/project myapp-build /swift-utils/tools-utils.sh build release

To run the application:

  • docker run -it -p 8080:8080 -v $PWD:/root/project -w /root/project myapp-run sh -c .build-ubuntu/release/EmojiJournalServer

Deploy to Bluemix

You can deploy your application to Bluemix using:

CloudFoundry CLI

You can deploy the application to Bluemix using the CloudFoundry command-line:

  1. Install the Cloud Foundry command-line (https://docs.cloudfoundry.org/cf-cli/install-go-cli.html)
  2. Ensure all configured services have been provisioned
  3. Run cf push from the project root directory

The Cloud Foundry CLI will not provision the configured services for you, so you will need to do this manually using the Bluemix web console (example) or the CloudFoundry CLI (cf create-service command)[http://cli.cloudfoundry.org/en-US/cf/create-service.html]. The service names and types will need to match your configuration.

Bluemix toolchain

You can also set up a default Bluemix Toolchain to handle deploying your application to Bluemix. This is achieved by publishing your application to a publicly accessible github repository and using the "Create Toolchain" button below. In this case configured services will be automatically provisioned, once, during toolchain creation.

Create Toolchain


All generated content is available for use and modification under the permissive MIT License (see LICENSE file), with the exception of SwaggerUI which is licensed under an Apache-2.0 license (see NOTICES.txt file).


This project was generated with generator-swiftserver v4.2.3.