Write Parse Cloud Code in Swift!
What is Cloud Code? For complex apps, sometimes you just need logic that isn’t running on a mobile device. Cloud Code makes this possible.
Cloud Code in ParseServerSwift is easy to use because it’s built using Parse-SwiftOG
and Vapor. ParseServerSwift provides many additional benefits over the traditional JS based Cloud Code that runs on the Node.js parse-server:
- Write code with the Parse-SwiftOG SDK vs the Parse JS SDK allowing you to take advantage of a modern SDK which is strongly typed
- Runs on a dedicated server/container, allowing the Node.js parse-server to focus on requests reducing the burden by offloading intensive tasks and providing a true microservice
- All Cloud Code is in one place, but automatically connects and supports the Node.js parse-server at scale. This circumvents the issues faced when using JS based Cloud Code with PM2
- Leverage the capabilities of server-side-swift with Vapor
Technically, complete apps can be written with ParseServerSwift, the only difference is that this code runs in your ParseServerSwift rather than running on the user’s mobile device. When you update your Cloud Code, it becomes available to all mobile environments instantly. You don’t have to wait for a new release of your application. This lets you change app behavior on the fly and add new features faster.
Setup a Vapor project by following the directions for installing and setting up your project on macOS or linux.
Then add ParseServerSwift to dependencies in your Package.swift file:
// swift-tools-version:5.6
import PackageDescription
let package = Package(
name: "YOUR_PROJECT_NAME",
platforms: [
.iOS(.v13),
.macCatalyst(.v13),
.macOS(.v10_15),
.tvOS(.v13),
.watchOS(.v6)
],
products: [
.library(name: "YOUR_PROJECT_NAME", targets: ["YOUR_PROJECT_NAME"])
],
dependencies: [
.package(url: "https://github.com/netreconlab/ParseServerSwift", .upToNextMajor(from: "0.8.4")),
.package(url: "https://github.com/vapor/vapor.git", .upToNextMajor(from: "4.76.2")),
.package(url: "https://github.com/netreconlab/Parse-Swift.git", .upToNextMajor(from: "5.7.0"))
]
...
targets: [
.target(
name: "YOUR_PROJECT_NAME",
dependencies: [
.product(name: "Vapor", package: "vapor"),
.product(name: "ParseSwift", package: "Parse-Swift"),
.product(name: "ParseServerSwift", package: "ParseServerSwift"),
]
),
.executableTarget(name: "App",
dependencies: [.target(name: "YOUR_PROJECT_NAME")],
swiftSettings: [
// Enable better optimizations when building in Release configuration. Despite the use of
// the `.unsafeFlags` construct required by SwiftPM, this flag is recommended for Release
// builds. See <https://github.com/swift-server/guides/blob/main/docs/building.md#building-for-production> for details.
.unsafeFlags(["-cross-module-optimization"], .when(configuration: .release))
]),
.testTarget(name: "YOUR_PROJECT_NAMETests", dependencies: [
.target(name: "YOUR_PROJECT_NAME"),
.product(name: "XCTVapor", package: "vapor"),
])
]
)Adding ParseServerSwift will allow you to quickly add routes for Parse Cloud Hook Functions and Triggers.
The following enviroment variables are available and can be configured directly or through .env, .env.production, etc. See the Vapor Docs for more details.
PARSE_SERVER_SWIFT_HOST_NAME: cloud-code # The name of your host. If you are running in Docker it should be same name as the docker service
PARSE_SERVER_SWIFT_PORT: # This is the default port on the docker image
PARSE_SERVER_SWIFT_DEFAULT_MAX_BODY_SIZE: 500kb # Set the default size for bodies that are collected into memory before calling your handlers (See Vapor docs for more details)
PARSE_SERVER_SWIFT_URLS: http://parse:1337/parse # (Required) Specify one of your Parse Servers to connect to. Can connect to multiple by seperating URLs with commas
PARSE_SERVER_SWIFT_APPLICATION_ID: appId # (Required) The application id of your Parse Server
PARSE_SERVER_SWIFT_PRIMARY_KEY: primaryKey # (Required) The master key of your Parse Server
PARSE_SERVER_SWIFT_WEBHOOK_KEY: webookKey # The webhookKey of your Parse Server
The webhookKey should match the webhookKey on the Parse Server.
The aforementioned environment variables automatically configure Parse-SwiftOG SDK. If you need a more custom configuration, see the documentation.
To levergage the aforementioned environment variables, you should modify entrypoint.swift in your project to look similar to below:
import Vapor
import Dispatch
import Logging
import NIOCore
import NIOPosix
import ParseServerSwift
@main
enum Entrypoint {
static func main() async throws {
var env = try Environment.detect()
try LoggingSystem.bootstrap(from: &env)
let app = try await Application.make(env)
// This attempts to install NIO as the Swift Concurrency global executor.
// You should not call any async functions before this point.
let executorTakeoverSuccess = NIOSingletons.unsafeTryInstallSingletonPosixEventLoopGroupAsConcurrencyGlobalExecutor()
app.logger.debug("Running with \(executorTakeoverSuccess ? "SwiftNIO" : "standard") Swift Concurrency default executor")
try await parseServerSwiftConfigure(
app,
using: exampleRoutes
)
try await app.execute()
try await app.asyncShutdown()
}
}If you want to pass the configuration parameters programitically, you can add a configure method to configure.swift should look similar to below:
public func configure(_ app: Application) async throws {
// Initialize ParseServerSwift
let configuration = try ParseServerConfiguration(app: app,
hostName: "hostName",
port: 8081,
applicationId: "applicationId",
primaryKey: "primaryKey",
webhookKey: hookKey,
parseServerURLString: "primaryKey")
try await ParseServerSwift.initialize(configuration, app: app)
// Add any additional code to configure your server here...
// register routes
try routes(app)
}ParseServerSwift is optimized to run in Docker containers. A sample docker-compose.yml demonstrates how to quickly spin up one (1) ParseServerSwift server with one (1) parse-hipaa servers and (1) hipaa-postgres database.
ParseSwift depends on FoundationNetworking when it is not built on Apple Platforms. Be sure to add the following lines to your Dockerfile release stage when building your own projects with ParseServerSwift.
- Fork this repo
- In your terminal, change directories into
ParseServerSwiftfolder - Type
docker-compose up - Accessing your containers:
- The first parse-hipaa server can be accessed at: http://localhost:1337/parse with the respective dashboard at: http://localhost:1337/dashboard/apps/Parse%20HIPAA/webhooks
- The default login for the dashboard is username:
parsewith password:1234 - To view all of your Cloud Code Functions and Hooks: click the
Parse-Hipaaapp, clickWebhooksto the left and you will see all of the example Cloud Code registered as webooks:
To start your server type, swift run in the terminal of the project root directory.
Apple's WWDC User Xcode for server-side development recommends creating Swift packages (15:26 mark) to house your models and share them between server and clients apps to reduce code duplication. To maximize Parse-Swift, it is recommended to not only add your models to your shared package, but to also add all of your queries (server and client). The reasons for this are:
- Parse-Swift queries on the client are cached by default; allowing Parse-Swift based apps to leverage cache to build zippier experiences
- When leveraging your shared queries in ParseServerSwift; they will never access local server cache as they always request the latest data from the Node.js Parse Server
- Calling Cloud-Code functions from clients do not ever access local cache as these are
POSTcalls to the Node.js Parse Server
Learn more about sharing models by reading the SwiftLee Blog.
If you have not created a shared package for your models, it is recommended to add all of your ParseObject's in a folder called Models similar to ParseServerSwift/Sources/ParseServerSwift/Models.
Be mindful that the ParseUser in ParseServerSwift should conform to ParseCloudUser. This is because the ParseCloudUser contains some additional properties on the server-side. On the client, you should always use ParseUser instead of ParseCloudUser. In addition, make sure to add all of the additional properties you have in your _User class to the User model. An example User model is below:
/**
An example `ParseUser`. You will want to add custom
properties to reflect the `ParseUser` on your Parse Server.
*/
struct User: ParseCloudUser {
var authData: [String: [String: String]?]?
var username: String?
var email: String?
var emailVerified: Bool?
var password: String?
var objectId: String?
var createdAt: Date?
var updatedAt: Date?
var ACL: ParseACL?
var originalData: Data?
var sessionToken: String?
var _failed_login_count: Int?
var _account_lockout_expires_at: Date?
}The GameScore model is below:
import Foundation
import ParseSwift
/**
An example `ParseObject`. This is for testing. You can
remove when creating your application.
*/
struct GameScore: ParseObject {
// These are required by ParseObject.
var objectId: String?
var createdAt: Date?
var updatedAt: Date?
var ACL: ParseACL?
var originalData: Data?
// Your own properties.
var points: Int?
// Implement your own version of merge.
func merge(with object: Self) throws -> Self {
var updated = try mergeParse(with: object)
if updated.shouldRestoreKey(\.points,
original: object) {
updated.points = object.points
}
return updated
}
}Adding routes for ParseHooks are as simple as adding routes in Vapor. ParseServerSwift provides some additional methods to routes to easily create and register Hook Functions and Hook Triggers. All routes should be added to the routes.swift file in your project. Example ParseServerSwift routes can be found in ParseServerSwift/Sources/ParseServerSwift/routes.swift.
Since ParseServerSwift is a Vapor server, it can be configured a number of different ways to suite your needs. Be sure to read through the vapor documentation. Some important features you may want to take advantage of are highlighed below:
- Route groups allows you to create a set of routes with a path prefix or specific middleware
- Route collections allow multiple routes and route groups to be organized in different files or modules
To learn more about creating groups and collections, checkout this blog.
Be sure to add import ParseSwift and import ParseServerSwift to the top of routes.swift
There will be times you will need to respond by sending an error to the Node.js Parse Server to propagate to the client. Sending errors can be accomplished by sending a ParseHookResponse. Below are two examples of sending an error:
// Note: `T` is the type to be returned if there is no error thrown.
// Standard Parse error with your own unique message
let standardError = ParseError(code: .missingObjectId, message: "This object requires an objectId")
return ParseHookResponse<T>(error: standardError) // Be sure to "return" the ParseHookResponse in your route, DO NOT "throw" the error.
// Custom error with your own unique code and message
let customError = ParseError(otherCode: 1001, message: "My custom error")
return ParseHookResponse<T>(error: customError) // Be sure to "return" ParseHookResponse in your route, DO NOT "throw" the error.Parse-Swift has a number of Swift Playgrounds to demonstrate how to use the SDK. Below are some notable Playgrounds specifically for Cloud Code that can be used directly in ParseServerSwift:
Cloud Code Functions can also take parameters. It's recommended to place all parameters in ParseServerSwift/Sources/ParseServerSwift/Models/Parameters
// A simple Parse Hook Function route that returns "Hello World".
app.post("hello",
name: "hello") { req async throws -> ParseHookResponse<String> in
// Note that `ParseHookResponse<String>` means a "successful"
// response will return a "String" type.
if let error: ParseHookResponse<String> = checkHeaders(req) {
return error
}
var parseRequest = try req.content
.decode(ParseHookFunctionRequest<User, FooParameters>.self)
// If a User made the request, fetch the complete user.
if parseRequest.user != nil {
parseRequest = try await parseRequest.hydrateUser(request: req)
}
// To query using the User's credentials who called this function,
// use the options() method from the parseRequest
let options = try parseRequest.options(req)
let scores = try await GameScore.query.findAll(options: options)
req.logger.info("Scores this user can access: \(scores)")
return ParseHookResponse(success: "Hello world!")
}// A Parse Hook Trigger route.
app.post("score", "save", "before",
object: GameScore.self,
trigger: .beforeSave) { req async throws -> ParseHookResponse<GameScore> in
// Note that `ParseHookResponse<GameScore>` means a "successful"
// response will return a "GameScore" type.
if let error: ParseHookResponse<GameScore> = checkHeaders(req) {
return error
}
var parseRequest = try req.content
.decode(ParseHookTriggerObjectRequest<User, GameScore>.self)
// If a User made the request, fetch the complete user.
if parseRequest.user != nil {
parseRequest = try await parseRequest.hydrateUser(request: req)
}
guard let object = parseRequest.object else {
return ParseHookResponse(error: .init(code: .missingObjectId,
message: "Object not sent in request."))
}
// To query using the primaryKey pass the `usePrimaryKey` option
// to ther query.
let scores = try await GameScore.query.findAll(options: [.usePrimaryKey])
req.logger.info("Before save is being made. Showing all scores before saving new ones: \(scores)")
return ParseHookResponse(success: object)
}
// Another Parse Hook Trigger route.
app.post("score", "find", "before",
object: GameScore.self,
trigger: .beforeFind) { req async throws -> ParseHookResponse<[GameScore]> in
// Note that `ParseHookResponse<[GameScore]>` means a "successful"
// response will return a "[GameScore]" type.
if let error: ParseHookResponse<[GameScore]> = checkHeaders(req) {
return error
}
let parseRequest = try req.content
.decode(ParseHookTriggerObjectRequest<User, GameScore>.self)
req.logger.info("A query is being made: \(parseRequest)")
// Return two custom scores instead.
let score1 = GameScore(objectId: "yolo",
createdAt: Date(),
points: 50)
let score2 = GameScore(objectId: "nolo",
createdAt: Date(),
points: 60)
req.logger.info("""
Returning custom objects to the user from Cloud Code instead of querying:
\(score1); \(score2)
""")
return ParseHookResponse(success: [score1, score2])
}
// Another Parse Hook Trigger route.
app.post("user", "login", "after",
object: User.self,
trigger: .afterLogin) { req async throws -> ParseHookResponse<Bool> in
// Note that `ParseHookResponse<Bool>` means a "successful"
// response will return a "Bool" type. Bool is the standard response with
// a "true" response meaning everything is okay or continue.
if let error: ParseHookResponse<Bool> = checkHeaders(req) {
return error
}
let parseRequest = try req.content
.decode(ParseHookTriggerObjectRequest<User, GameScore>.self)
req.logger.info("A user has logged in: \(parseRequest)")
return ParseHookResponse(success: true)
}
// A Parse Hook Trigger route for `ParseFile`.
app.on("file", "save", "before",
trigger: .beforeSave) { req async throws -> ParseHookResponse<Bool> in
// Note that `ParseHookResponse<Bool>` means a "successful"
// response will return a "Bool" type. Bool is the standard response with
// a "true" response meaning everything is okay or continue. Sending "false"
// in this case will reject saving the file.
if let error: ParseHookResponse<Bool> = checkHeaders(req) {
return error
}
let parseRequest = try req.content
.decode(ParseHookTriggerRequest<User>.self)
req.logger.info("A ParseFile is being saved: \(parseRequest)")
return ParseHookResponse(success: true)
}
// Another Parse Hook Trigger route for `ParseFile`.
app.post("file", "delete", "before",
trigger: .beforeDelete) { req async throws -> ParseHookResponse<Bool> in
// Note that `ParseHookResponse<Bool>` means a "successful"
// response will return a "Bool" type. Bool is the standard response with
// a "true" response meaning everything is okay or continue.
if let error: ParseHookResponse<Bool> = checkHeaders(req) {
return error
}
let parseRequest = try req.content
.decode(ParseHookTriggerRequest<User>.self)
req.logger.info("A ParseFile is being deleted: \(parseRequest)")
return ParseHookResponse(success: true)
}
// A Parse Hook Trigger route for `ParseLiveQuery`.
app.post("connect", "before",
trigger: .beforeConnect) { req async throws -> ParseHookResponse<Bool> in
// Note that `ParseHookResponse<Bool>` means a "successful"
// response will return a "Bool" type. Bool is the standard response with
// a "true" response meaning everything is okay or continue.
if let error: ParseHookResponse<Bool> = checkHeaders(req) {
return error
}
let parseRequest = try req.content
.decode(ParseHookTriggerRequest<User>.self)
req.logger.info("A LiveQuery connection is being made: \(parseRequest)")
return ParseHookResponse(success: true)
}
// Another Parse Hook Trigger route for `ParseLiveQuery`.
app.post("score", "subscribe", "before",
object: GameScore.self,
trigger: .beforeSubscribe) { req async throws -> ParseHookResponse<Bool> in
// Note that `ParseHookResponse<Bool>` means a "successful"
// response will return a "Bool" type. Bool is the standard response with
// a "true" response meaning everything is okay or continue.
if let error: ParseHookResponse<Bool> = checkHeaders(req) {
return error
}
let parseRequest = try req.content
.decode(ParseHookTriggerObjectRequest<User, GameScore>.self)
req.logger.info("A LiveQuery subscription is being made: \(parseRequest)")
return ParseHookResponse(success: true)
}
// Another Parse Hook Trigger route for `ParseLiveQuery`.
app.post("score", "event", "after",
object: GameScore.self,
trigger: .afterEvent) { req async throws -> ParseHookResponse<Bool> in
// Note that `ParseHookResponse<Bool>` means a "successful"
// response will return a "Bool" type. Bool is the standard response with
// a "true" response meaning everything is okay or continue.
if let error: ParseHookResponse<Bool> = checkHeaders(req) {
return error
}
let parseRequest = try req.content
.decode(ParseHookTriggerObjectRequest<User, GameScore>.self)
req.logger.info("A LiveQuery event occured: \(parseRequest)")
return ParseHookResponse(success: true)
}