Skygear
API References
Forum
Search…
Skygear Documentation
Set up
Install and Configure skycli
Install SkygearSDK
quick start
Deploying your first Node.js server to Skygear with pre-configured template
Deploy a Dart server with self-defined Dockerfile
Host a blog site on Skygear (Auth Gear, your frontend + backend + database)
HOW TO
How to connect to a managed database on Skygear
How to call API of a deployed service on Skygear
How to upload templates to Skygear
How to view the logs of your microservices
How to set up a custom domain
Auth
Exchange of Session with User Info at Gateway
User & Identity
API Clients & Key
External Service Providers
Web-hooks
skycli
Introduction
List of Commands
Template Management
skygear.yaml
Routing
Deployment Image
Secret Management
App Management
Team Management
Cross-Origin policy
Microservices
Secrets
Skygear HTTP Headers
Support
API References
Forum
Stack Overflow
Email us
Powered By
GitBook
Routing
Developers can specifies the routing configuration of the app. The routing behavior is based on simple rules:
The request path is matched against configured
path
prefix.
The longest matched prefix would be used.
Path with
/_
prefix is reserved for Skygear built-in APIs.
For example, in the following configuration:
1
deployments
:
2
-
name
:
backend
3
path
:
/api
4
port
:
8080
5
# ...
6
-
name
:
frontend
7
path
:
/
8
port
:
8080
9
# ...
Copied!
Requests would be routed to:
/
: micro-service
frontend
/api
: micro-service
backend
/login
: micro-service
frontend
/api/blogs
: micro-service
backend
/_auth/login
: Skygear Auth APIs
Requests with unmatched paths would be responded with status code 404.
skycli - Previous
skygear.yaml
Next
Deployment Image
Last modified
2yr ago
Copy link