Security News
PyPI Introduces Digital Attestations to Strengthen Python Package Security
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
FLY
is a library for back-end development.
Require
node >= 8
## Yarn
$ yarn global add fly
$ fly new example
$ cd example
index.js
module.exports = {
main: (event, ctx) => {
return {
status: 200,
body: 'hello from fly'
}
},
configHttp: {
path: '/'
}
}
$ fly run http↙
┌────────┬────────────────┬────────┐
│ Method │ Path │ Fn │
│ GET │ / │ index │
└────────┴────────────────┴────────┘
[SERVICE] Http Server
NAME: project
TYPE: http
ADDRESS: http://127.0.0.1:5000
PID: 55195
ENV: development
If you change index.js, the function will hot reload without restart. this feature will disabled when NODE_ENV is not
<empty>
ordevelopment
❏ FLY 4.1.0
Usage:
fly <command> [--options]
Commands:
call <fn> Call function
<fn> Function name to call
--type string Set event type: such as http
--data,-d string Event data, support JSON and URL-QUERY-ENCODED
--timeout,-t number Execution timeout
--error,-e Show full error
debug <service> Debug online server
<service> Service type
--filter,-f string
get <fn> Get function info
<fn> Function name
help Show help
list [type] List functions
log [service] Show service log
new [dir] Create new fly project
[dir] Dir name
--force Force create when dir exists
--source,-s string Select source to create. support: http (default), project
reload [service] Reload service
restart [service] Restart service
run [service] Run service in foregroud
--instance,-i number The instance number
--bind,-b string Bind address
--port,-p number Bind port
start [service] Start service as daemon
--instance,-i number The instance number
--bind,-b string Bind address
--port,-p number Bind port
--cron-restart string Schedule time to restart with cron pattern
status [service] Show service status
stop [service] Stop service
test [fn] Test functions
<fn> Function name
--timeout number
--error,-e Show full error
Event can be anything, but must can be JSONify
Http Event
method: String # request http method, lowercase
path: String # request http path
origin: String # request http origin
host: String # request http host
domain: String # request domain
url: String # request full url
protocol: String # request protocol
port: Number # request port
ip: String # request ip
headers: Object # request headers
body: Object # request body
files: Object # request files
query: Object # request query
search: String # request search string without ?
cookies: Object # request cookies
Http Config
method: String # Set method, eg: get, post, put, delete
path: String # Set path, eg: /api
domain: String | Array # Set domain you want supply service
cache: Boolean | Number # Set page cache header, `true` is 600 seconds
cors: Boolean | String # Set http CORS header, `true` is for all origin, String set origin, object set params
origin: String
headers: String
methods: String
upload:
allowTypes: Array # mimetypes, eg: ['png', 'image/jpeg']
maxSize: Number # maxSize, default is 100mb
Command Event
args: Object # command args, eg: "--help"
params: Object # command params, eg: "call <param>", param will pass as params.param
Command Config
_: String # command declare, eg: "call <param>"
args: Object # command args declares: `"--help": Boolean`
alias: Object # command alias declares, eg: `"--help": '-h'`
descriptions: Object # command descriptions
_: String # command description
<param>: String # param description
<args>: String # arg description
Command Example
module.exports = {
main () {
const command = event.params.command
const showFull = event.args.full
# logic
},
configCommand: {
_: 'help <command>',
args: {
'--full': Boolean
},
alias: {
'--full': '-f'
},
descriptions: {
_: 'Show help for commands',
'<help>': 'Command name'
'--full': 'Show full descriptions'
}
}
}
Cron Event
time: timestamp
Cron Config
time: '* * * * *' # See format defintion https://en.wikipedia.org/wiki/Cron
timeout: 60 # Maximum time limit
Cron Example
module.exports = {
main() {
// tick on every 30min
},
configCron: {
time: '*/30 * * * *'
}
}
Error handle Example
Example to handle error with
Sentry
const Sentry = require('@sentry/node')
Sentry.init({
dsn: 'http://appkey@sentry.io'
})
module.exports = {
configError: true,
main (event) {
const err = event
if (err instanceof Error) {
Sentry.captureException(err)
} else if (typeof err !== 'undefined') {
Sentry.captureMessage(util.inspect(err, { depth: null, breakLength: Infinity }))
}
}
}
Connect db When app startup
module.exports = {
configStartup: true,
async main (){
ctx.db = await DB.connect()
console.log('db connected')
}
}
Delete tmp files when shutdown
module.exports = {
configShutdown: true,
main () {
return deleteTempFiles()
}
}
Optional. You can place
fly.yml
in directory to overwrite funciton's config
fly.yml
project:
ignore:
- "example/**"
# config overwrite for service function
service:
$http:
port: 6000
title: 'My http server'
# config overwrite for http function
http:
login:
method: post
path: /api/login
cors: true
You can write
<name>.test.js
in same folder then runfly test
it will test automatically
index.test.js
index
.test.js file name is same likeindex.js
orindex.file.js
, keep them in same folder
const assert = require('assert')
module.exports = {
tests: [{
name: 'Check result code',
event: {},
test (result) {
assert.strictEqual(result.code, 0)
}
}]
}
Execute test
$ fly test
◼︎ 2 functions to test
√ [1] +index 1/1 passed
√ 1) Check code === 0 (2ms)
√ [2] +userLogin 2/2 passed
√ 1) status === 1 (1ms)
√ 2) invalid username trigger validate error (1ms)
√ 2/2 functions passed
You can use in Nodejs and call fly function directly
const Fly = require('node-fly')
const fly = new Fly('/dir')
await fly.call('test', {host: 'api.com'})
Function Definition
extends: String # Extends from function, start with @ indicate the parent fly
retry: Number|Boolean # Retry count, true is 3
perload: String|Array # Preload some functions before (add in v4.1)
main: Function # Main call -> (event, ctx)
props: # Props validate definitions
validate: Function # Validate
before: Function # Before filter
after: Function # After filter
catch: Function # Error catch
config<Event>: Object|Boolean|Function # Startup event
before<Event>: Function # Before filter
after<Event>: Function # After filter
validate<Event>: Function # Validate event
catch<Event>: Function # Error catch
props<Event>: Object # Props definetions for event
# same as props, but only for given event
Example
createUser.js
Create user with info
{
/**
* Define event types
*/
props: {
id: Number,
email: {
type: 'email',
lowercase: true,
message: 'Email invalid'
},
name: {
type: String,
default: 'User'
},
avatar: {
type: String,
default: 'User'
},
bornDate: {
type: Date,
format: 'value'
},
info: {
type: 'Object',
props: {
title: String,
}
}
},
// Extends from appbase for initial functions
extends: 'authHttpUser',
/**
* Main function
*/
main(event) {
const db = this.db()
db.collections('user').insertOne(event)
},
/**
* Config before http
*/
beforeHttp(event) {
# Transform query or body to main
return event.query || event.body
},
/**
* Config after http
*/
afterHttp(event) {
return {
code: 0,
data: event
}
},
/**
* Config before command
*/
beforeCommand(event) {
return event.args
},
/**
* Config after command
*/
afterCommand(event) {
Object.keys(event).forEach(name => console.log(`${name}: ${event[name]}`))
},
/**
* Config http event
*/
configHttp: {
method: 'post',
path: '/api/createUser'
},
/**
* Config command event
*/
configCommand: {
_: 'create',
args: {
'--name': String,
'--email': String,
'--id': Number
}
}
}
eventId: String # Event ID
eventType: String # Event Type:http, command, null is internal
originalEvent: Event # OriginalEvent
parentEvent: Event # Parent Event
trace: Object # Current trace
call: Function # Invoke function
list: Function # List functions
get: Function # Get function
error: Function # Trigger error internal
return: Function # Trigger error internal
super: Function # Call parent method when extend other
<fn>: Function # The functions imported
Define validate props
to validate event, throw FlyValidateError
if validate failed.
Define
Define properties in
props
type: String, # Support: email, date, alpha, alphanumeric, base64, base32, enum, float, number, ip, json, md5, phonenumber, port, url, uppercase, lowercase, macaddress, hexcolor, locale, hex, hash, fadn, ascii, validator
# Pre transform options
pretrim: Boolean # Pre trim
before: Function # Before filter
validate: Function # Custom validator with (input, definition)
# String options
lowercase: Boolean # Auto convert lowercase, default is false
uppercase: Boolean # Auto convert uppercase, default is false
trim: Boolean # Trim
# Hash options
algorithm: String # Support: md5, sha1, sha256, sha512
# Pattern options
enum: Array[String] # Enum options
# Date options
format: String # Support: date, datetime, unix, value, ios, [YY-MM-DD]
# After transform options
after: Function # After transform options
# Global options
default: String # Default value if not exists
message: String # Message will throw as FlyValidateError(message),
# Nested options
props: Object # Nested props definetions
FlyValidateError
{
name: "FlyValidateError",
message: "validate failed: filed1, filed2",
errors: [
{
name: "filed1",
type: "string",
message: "filed1 validate error"
}
]
}
Copyright (c) 2019 hfcorriez hfcorriez@gmail.com
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
For back-end development
We found that fly demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.