Everything a newbie should know
Welcome to the Phoenix platform. Here you will learn how to get started with Phoenix.
A "Project" within Phoenix separates the back-end of one application from another. Generally you should have separate projects per application, but if you have multiple applications (eg an iOS and an Android application) that reflect the same brand, these applications can share the same project as they most likely will want to share the same back end data.
To create a new project within Phoenix, complete the following steps:
A user account is required to access either the Phoenix Dashboard, or the Phoenix API’s. Users can be humans or applications. Human users log into Phoenix with a username and password, whereas Application Users access the Phoenix API with API credentials. Each application should have it's own set of Credentials so you can control access to your Project data.
To create a new user within Phoenix, complete the following steps:
Users of Phoenix are restricted to a Role Based Access Control (RBAC) security policy. Users must be assigned Role(s) and/or Privleges to gain authorisation to Phoenix API operations. To assign roles & privleges, follow these steps:
Application Users require API Credentials to authenticate to the Phoenix API’s.
Each Phoenix module exposes SOAP and WEB endpoints. Generally speaking:
The Phoenix API's support authentication via the OAuth 2 protocol. Currently the Resource Owner Password Credentials and Client Credentials grant type flows are supported.
The Tigerspike Phoenix SDK (TSPhoenix) is an iOS SDK for Tigerspike Phoenix Platform. providing a path to success when building iPhone / iPad apps integrations with Phoenix Platform. The SDK allows you as a developer to interface with objective-level APIs and focus your time and energy on the UI
The service helper provides a simple helper concept for consuming Phoenix abstracting away the core framework fundamentals in a simple and DRY manner whilst advocating best patterns and practices.