| 1 | {
|
| 2 | "name": "clay-cli",
|
| 3 | "version": "2.0.14",
|
| 4 | "description": "Web Tool to publish and manage Web Sites and Apps",
|
| 5 | "bin": {
|
| 6 | "clay": "bin/clay.js"
|
| 7 | },
|
| 8 | "dependencies": {
|
| 9 | "chalk": "~0.5.1",
|
| 10 | "cheerio": "~0.18.0",
|
| 11 | "dotenv": "^1.2.0",
|
| 12 | "gulp": "~3.8.10",
|
| 13 | "gulp-api-log": "~0.1.1",
|
| 14 | "gulp-assetpaths": "~0.1.1",
|
| 15 | "gulp-awspublish": "~1.0.6",
|
| 16 | "gulp-rename": "~1.2.0",
|
| 17 | "gulp-replace": "~0.5.0",
|
| 18 | "gulp-rev-all": "~0.7.1",
|
| 19 | "gulp-util": "~3.0.1",
|
| 20 | "gulp-zip": "~2.0.2",
|
| 21 | "jsforce": "~1.3.1",
|
| 22 | "jszip": "~2.4.0",
|
| 23 | "minimist": "^1.2.0",
|
| 24 | "open": "0.0.5",
|
| 25 | "q": "~1.1.2",
|
| 26 | "superagent": "~0.21.0",
|
| 27 | "tape": "~3.0.3",
|
| 28 | "through2": "~0.6.3",
|
| 29 | "vinyl-source-stream": "~1.0.0",
|
| 30 | "win-spawn": "^2.0.0",
|
| 31 | "yargs": "~1.3.3"
|
| 32 | },
|
| 33 | "devDependencies": {
|
| 34 | "tap": "~0.4.13"
|
| 35 | },
|
| 36 | "scripts": {
|
| 37 | "test": "tap test/*.js"
|
| 38 | },
|
| 39 | "repository": {
|
| 40 | "type": "git",
|
| 41 | "url": "git+https://github.com/3vot/clay.git"
|
| 42 | },
|
| 43 | "author": "",
|
| 44 | "license": "BSD-2-Clause",
|
| 45 | "bugs": {
|
| 46 | "url": "https://github.com/3vot/clay/issues"
|
| 47 | },
|
| 48 | "readme": "Clay Command Line Tool\n========\n\nCommand Line tool to build and Publish Web and Mobile Applications\n\n\n## What is clay\n\nClay is used to publish pages, apps and content to the web fast and easy.\n\nClay can also be used to build javascript/html5 apps with a streamlined process that takes advantage of gulp plugins.\n\n## How can I use Clay\n\nFirst setup your project, then use clay and gulp plugin to automate the most repetitive tasks while building apps and finally use Clay to upload the project to the web.\n\n## Creating an App\nAfter registering with Clay - create and app using `clay create APP_NAME` where APP_NAME is the name of your app.\n\nOnce you are ready to `clay preview` your app - it will be available in APP_NAME.3votapp.com - where APP_NAME is the name of your app.\n\nThen from your domain - simply create a CNAME record that points to APP_NAME.3votapp.com. Once that's done you'll be able to run apps from http://smile.cocacola.com for example.\n\n## Gulp and Plugins\nUse project http://github.com/3vot/r3_demo to setup your new project.\n\nGulp is optional and completely under developers control - in the end what Clay does is it gets the contents of the `dist` folder and uploads it. \n\n\n\n## Salesforce\nClay is useful to build Salesforce Applications based in Visualforce - it contains a set of plugins to login, run a local server, upload visualforce pages and static resources.\n\nIt operates the whole livecycle of the app from development to deployment - apps can be build like regular HTML5/Javascript apps and then published to Salesforce/Salesforce1 as Visualforce Pages.\n\nUse project http://github.com/3vot/vf_demo to setup your new project.\n\n## Commands\n\n### clay\nRuns the default Gulp task - is similar as running gulp.\n\n### clay preview\nRuns the `gulp dist` task if it exists and then uploads the contents of the `dist` folder into APP_NAME_stage.3votapp.com. \n\nThe preview adds a _stage suffix to APP_NAME, this is done so we are able to have a staging sharable version.\n\n### clay publish\nRuns the `gulp dist` task if it exists and then uploads the contents of the `dist` folder into APP_NAME.3votapp.com. \n\n## Salesforce Commands\n\nSalesforce commands are similar - just add the salesforce keyword\n\n`clay salesforce` - starts local development server\n\n`clay salesforce publish` - published contents of `dist` folder as visualforce page + static resources\n\n\n## Gulp Tasks\nTo run a gulp task from Clay - simply type the task name after clay. `clay images` - just make sure the task's name is not salesforce, preview or publish.\n\n## .env file\nEvery project needs to have a .env file - this file contains project specific information. Here is an example:\n```\n```\n\nMake sure to add the `.env` file entry to `.gitignore` file on the projects root.\n\n## .env file for Salesforce\nWhen used in Salesforce the .env file also requires the options SF_USERNAME, SF_PASSWORD AND SF_HOST. SF_PASSWORD may include the security token right after the password.\n\n\n",
|
| 49 | "readmeFilename": "README.md",
|
| 50 | "gitHead": "8907b2e63ac93e616981d4add9f747554f928c82",
|
| 51 | "homepage": "https://github.com/3vot/clay#readme",
|
| 52 | "_id": "clay-cli@2.0.12",
|
| 53 | "_shasum": "760b4ce1f82eb5bb91e3cc3723bda91d9db611aa",
|
| 54 | "_from": "clay-cli@*"
|
| 55 | }
|