dpd-startup
Advanced tools
Comparing version 1.0.1 to 1.0.2
@@ -0,0 +0,0 @@ var Resource = require('deployd/lib/resource'), |
{ | ||
"name": "dpd-startup", | ||
"version": "1.0.1", | ||
"version": "1.0.2", | ||
"description": "Deployd module to create event scripts that are run on startup, after deployd starts your project, regardless of any requests coming in.", | ||
"main": "index.js", | ||
"dependencies": { | ||
"peerDependencies": { | ||
"deployd": "^1.0.0" | ||
@@ -8,0 +8,0 @@ }, |
@@ -21,2 +21,4 @@ ## Start-up Code Resource for deployd | ||
Use [dpd-dashboard](https://www.npmjs.org/package/dpd-startup) to add a **Start-up Module**. The name doesn't matter and you can have as many as you need. | ||
You can write your startup code inside the `Index` event. The code will be run on startup. You will have access to the `dpd` object like in any other event script. | ||
@@ -28,2 +30,4 @@ | ||
So, make sure your startup logic is valid for this purpose. Otherwise, restart your project manually every time, or do not edit the script using `dpd-dashboard`. | ||
So, make sure your startup logic is valid for this purpose. Otherwise, restart your project manually every time, or do not edit the script using `dpd-dashboard`. | ||
The order the startup scripts are ran in is not guaranteed. If you need a particular order, and would like to split your startup script into smaller parts, you can combine this with [dpd-codemodule](https://www.npmjs.org/package/dpd-codemodule) and write your logic inside **Code Resources**, which you can then use from your **startup module**. |
Sorry, the diff of this file is not supported yet
4295
31
- Removeddeployd@^1.0.0