prestoscript 0.0.1
Sign up to get free protection for your applications and to get access to all the features.
- data/readme.txt +113 -0
- data/temp/file.rb +4 -0
- metadata +62 -0
data/readme.txt
ADDED
@@ -0,0 +1,113 @@
|
|
1
|
+
PrestoScript Command Line Runner V 1.0
|
2
|
+
======================================
|
3
|
+
|
4
|
+
Usage:
|
5
|
+
|
6
|
+
prestoscript COMMAND [args...]
|
7
|
+
|
8
|
+
|
9
|
+
COMMAND
|
10
|
+
-----------------------------------
|
11
|
+
get Get a stored script
|
12
|
+
info Get info about your account
|
13
|
+
run Run a script
|
14
|
+
store Store a script
|
15
|
+
|
16
|
+
Basic configuration:
|
17
|
+
|
18
|
+
Your PrestoScript.com API key and secret key can be stored on one of two
|
19
|
+
ways.
|
20
|
+
|
21
|
+
1. Environment variables.
|
22
|
+
|
23
|
+
PRESTOSCRIPT_API_KEY
|
24
|
+
PRESTOSCRIPT_SECRET_KEY
|
25
|
+
|
26
|
+
2. In prestoscript.ini
|
27
|
+
|
28
|
+
prestoscript.ini must be in the current search path and should contain:
|
29
|
+
|
30
|
+
API_KEY=...
|
31
|
+
SECRET_KEY=...
|
32
|
+
|
33
|
+
|
34
|
+
GET command
|
35
|
+
-----------------------------------
|
36
|
+
|
37
|
+
prestoscript get <script_key>
|
38
|
+
|
39
|
+
script_key The key name of the script to get from the server.
|
40
|
+
The name you supply should be script key name used with STORE.
|
41
|
+
|
42
|
+
INFO command
|
43
|
+
-----------------------------------
|
44
|
+
|
45
|
+
prestoscript info
|
46
|
+
|
47
|
+
RUN command
|
48
|
+
-----------------------------------
|
49
|
+
|
50
|
+
prestoscript run [-http] <script_path>
|
51
|
+
|
52
|
+
Run a script and output the result to stdout.
|
53
|
+
|
54
|
+
It will also save two types of log files.
|
55
|
+
|
56
|
+
1. <script_key>.log.csv will contain the CSV version of the log file. This
|
57
|
+
is the raw format.
|
58
|
+
|
59
|
+
2. <script_key>.log.html will contain a convenient HTML representation.
|
60
|
+
|
61
|
+
script_path The local file name of a script to run
|
62
|
+
-http Include HTTP header information in the output. This is useful
|
63
|
+
if your script modifies HTTP header information and you wish
|
64
|
+
to see the results locally before storing the script for
|
65
|
+
production.
|
66
|
+
|
67
|
+
STORE command
|
68
|
+
-----------------------------------
|
69
|
+
|
70
|
+
prestoscript store <script_path>
|
71
|
+
|
72
|
+
Store a local script to the PrestoScript.com cloud. Using this store method
|
73
|
+
makes your script publicly executable through the Resto gateway. This is how
|
74
|
+
you deploy your script if you are doing more than simple batch processing.
|
75
|
+
|
76
|
+
The script will be stored at PrestoScript.com with a script key matching the
|
77
|
+
file name of your script. Your script can then be run through the Resto
|
78
|
+
HTTP/HTTPS gateway using the script key name.
|
79
|
+
|
80
|
+
When you store a script, the script key name must be unique for all of
|
81
|
+
PrestoScript.com. To avoid confusion, you must name your local file
|
82
|
+
the same thing. It must also follow URL-style naming rules. That is, you
|
83
|
+
may not use any special characters like ? / : etc.
|
84
|
+
|
85
|
+
Finally, you may hide the prestoscript.com name from your users by
|
86
|
+
creating a CNAME to resto.prestoscript.com if you wish. In this case, your
|
87
|
+
script name must be compatible with domain naming rules too.
|
88
|
+
|
89
|
+
Example 1 (normal):
|
90
|
+
|
91
|
+
Suppose you have a local script file, fancy_script.psml. The script key is
|
92
|
+
fancy_script.
|
93
|
+
|
94
|
+
You would run:
|
95
|
+
|
96
|
+
prestoscript store fancy_script.psml
|
97
|
+
|
98
|
+
You would access this through:
|
99
|
+
http://resto.prestoscript.com/fancy_script
|
100
|
+
|
101
|
+
Example 2 (CNAME):
|
102
|
+
|
103
|
+
This time, you made a CNAME entry for www.fancy_script.com and have
|
104
|
+
pointed it at resto.prestoscript.com. Now your local script file name is
|
105
|
+
www.fancy_script.com.psml.
|
106
|
+
|
107
|
+
You would run:
|
108
|
+
|
109
|
+
prestoscript store www.fancy_script.com.psml
|
110
|
+
|
111
|
+
You can access this script either way:
|
112
|
+
http://www.fancy_script.com
|
113
|
+
http://resto.prestoscript.com/www.fancy_script.com
|
data/temp/file.rb
ADDED
metadata
ADDED
@@ -0,0 +1,62 @@
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
2
|
+
name: prestoscript
|
3
|
+
version: !ruby/object:Gem::Version
|
4
|
+
version: 0.0.1
|
5
|
+
platform: ruby
|
6
|
+
authors:
|
7
|
+
- Benjamin Allfree
|
8
|
+
autorequire:
|
9
|
+
bindir: ./
|
10
|
+
cert_chain: []
|
11
|
+
|
12
|
+
date: 2008-06-05 00:00:00 +00:00
|
13
|
+
default_executable:
|
14
|
+
dependencies:
|
15
|
+
- !ruby/object:Gem::Dependency
|
16
|
+
name: fastercsv
|
17
|
+
version_requirement:
|
18
|
+
version_requirements: !ruby/object:Gem::Requirement
|
19
|
+
requirements:
|
20
|
+
- - ">="
|
21
|
+
- !ruby/object:Gem::Version
|
22
|
+
version: 0.0.0
|
23
|
+
version:
|
24
|
+
description:
|
25
|
+
email: benles@bldigital.com
|
26
|
+
executables: []
|
27
|
+
|
28
|
+
extensions: []
|
29
|
+
|
30
|
+
extra_rdoc_files:
|
31
|
+
- readme.txt
|
32
|
+
files:
|
33
|
+
- temp/file.rb
|
34
|
+
- readme.txt
|
35
|
+
has_rdoc: true
|
36
|
+
homepage: http://rubyforge.org/projects/prestoscript/
|
37
|
+
post_install_message:
|
38
|
+
rdoc_options: []
|
39
|
+
|
40
|
+
require_paths:
|
41
|
+
- lib
|
42
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
43
|
+
requirements:
|
44
|
+
- - ">="
|
45
|
+
- !ruby/object:Gem::Version
|
46
|
+
version: "0"
|
47
|
+
version:
|
48
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
49
|
+
requirements:
|
50
|
+
- - ">="
|
51
|
+
- !ruby/object:Gem::Version
|
52
|
+
version: "0"
|
53
|
+
version:
|
54
|
+
requirements: []
|
55
|
+
|
56
|
+
rubyforge_project: prestoscript
|
57
|
+
rubygems_version: 1.1.1
|
58
|
+
signing_key:
|
59
|
+
specification_version: 2
|
60
|
+
summary: Command line tools for PrestoScript scripting language
|
61
|
+
test_files: []
|
62
|
+
|