a8ed60296a
If --fromgit=<url> is specified: - Shallow-clone the repo. - Export the tree from the clone. - Run .cdbrelease.lua hook in the root of the tree. - Merge any data returned into config. .cdbrelease.lua can do more-or-less whatever lua allows (e.g. using dofile, filesystem access, etc.) to figure out the settings it wants to provide. This allows it to do things like include files from mods for shared versioning logic and perform more complex version number calculations, like NodeCore does. It could also be a security risk, so this should be used only on repos that the user has good control over. The canonical example is for .cdbrelease.lua to compute its own version number from stats that get baked into the file by the export step based on .gitattributes. Things like defaulting the pacakge name and author are possible too. Settings that are already explicitly specified at an earlier step are ignored from .cdbrelease.lua.
16 lines
369 B
JSON
16 lines
369 B
JSON
{
|
|
"name": "cdbrelease",
|
|
"version": "1.0.0",
|
|
"description": "release to minetest contentdb from the command line",
|
|
"main": "index.js",
|
|
"author": "Aaron Suen <warr1024@gmail.com>",
|
|
"license": "ISC",
|
|
"dependencies": {
|
|
"cheerio": "^1.0.0-rc.2",
|
|
"fs-extra": "^7.0.1",
|
|
"minimist": "^1.2.0",
|
|
"needle": "^2.2.4",
|
|
"tmp-promise": "^1.0.5"
|
|
}
|
|
}
|