website logo
⌘K
Introduction
Getting started
πŸ“Reference
Data API
Cache API
Search API
Storage API
Queue API
Crawler API
πŸ”‘Authentication
βœ”οΈConfiguration
⚑Contributing to hyper
πŸ”ŒBuilding your own adapter
Code of Conduct
hyper RFCs
Style Guide
Bugs
Before Submitting A Bug Report
Building your own plugin
API Clients
Build your own client πŸ› οΈ
hyper connect
NodeJS Client πŸš€
Deno Client πŸ¦•
Middleware
Hooks
🚒Deploy
Deploy hyper on Render
Deploy hyper on AWS
Deploy hyper on Digital Ocean
Deploy hyper on Google Cloud
Deploy hyper on Azure
πŸ“œChangelog
FAQ
πŸ“•Terminology
Parameters
What is REST?
What is JSON?
πŸ“˜Glossary
Docs powered byΒ archbeeΒ 
4min

Configuration

Description

ο»Ώ

Configuration is one of the most awesome bits of hyper63. The goal of the configuration file is to be flexible and powerful, but easy to use. In the configuration file, you can define the app integration, the adapters, and middleware. You can also specify where you would like to send notifications so that you can have full observability into hyper63. The file should always be named hyper.config.js

ο»Ώ

Example

ο»Ώ

hyper.config.js

JS
|

In the configuration file you map your adapters to specific ports, these ports contain the rules for the services, and the adapters contain the implementation.

Summary

The config file is the core manifest for hyper, it pulls all of the adapters into the fold and configures, and applies them to the core module.

Need specific help? You can always reach out to our support team for any additional assistance at checkout our help deskο»Ώ

Updated 15 Mar 2022
Did this page help you?
Yes
No
UP NEXT
Contributing to hyper
Docs powered byΒ archbeeΒ 
TABLE OF CONTENTS
Description
Example
Summary