upstart-exporter 0.0.5 → 0.0.6

Sign up to get free protection for your applications and to get access to all the features.
data/README.md CHANGED
@@ -4,11 +4,11 @@ Gem for exporting user-scripts as Upstart scripts
4
4
  Purpose
5
5
  -------
6
6
 
7
- It is often neccessary to run some supporting background tasks for rails projects alongside with the webserver. One of the solutions is use of Foreman gem, which allows to export tasks as Upstart scripts. This solution is dangerous,because it requires root priveleges for foreman executable (in order to add scripts to /etc/init), so it the depoloing user to run any code as root (by placing appropriate script into /etc/init).
7
+ It is often neccessary to run some supporting background tasks for rails projects alongside with the webserver. One of the solutions is use of Foreman gem, which allows to export tasks as Upstart scripts. This solution is dangerous, because it requires root priveleges for foreman executable (in order to add scripts to /etc/init), so it allows the exporting user to run any code as root (by placing appropriate script into /etc/init).
8
8
 
9
- This gem is an attempt to provide a safe way for installing backround jobs, so that they run under some fixed user wwithout root priveleges.
9
+ This gem is an attempt to provide a safe way for installing backround jobs, so that they run under some fixed user without root priveleges.
10
10
 
11
- The only interface to the gem is the script it provides.
11
+ The only interface to the gem is the script(*upstart-export*) it provides.
12
12
 
13
13
  Installing
14
14
  ----------
@@ -32,7 +32,7 @@ The config is not installed by default. If this config is absent, the default va
32
32
  upstart_dir: /etc/init/
33
33
  run_user: service
34
34
 
35
- To give a user (i.e. deployuser) ability to use this script, one can place
35
+ To give a certain user (i.e. deployuser) ability to use this script, one can place the following lines into sudoers file:
36
36
 
37
37
  # Commands required for manipulating jobs
38
38
  Cmnd_Alias UPSTART = /sbin/start, /sbin/stop, /sbin/restart
@@ -68,16 +68,17 @@ To export this file one should run
68
68
 
69
69
  sudo upstart-export -p ./myprocfile -n myapp
70
70
 
71
- -hore myapp is the application name. This name only affects the names of generated files. For security purposes, app name is also allowed to contain only letters, digits and underscores. Assuming that default options are used, the following files and folders will be generated:
71
+ where _myapp_ is the application name. This name only affects the names of generated files. For security purposes, app name is also allowed to contain only letters, digits and underscores. Assuming that default options are used, the following files and folders will be generated:
72
72
 
73
73
  in /etc/init/:
74
+
74
75
  fb-myapp-my_another_tail_cmd-real.conf
75
76
  fb-myapp-my_another_tail_cmd.conf
76
77
  fb-myapp-my_tail_cmd-real.conf
77
78
  fb-myapp-my_tail_cmd.conf
78
79
  fb-myapp.conf
79
80
 
80
- in /var/local/upstart\_helpers:
81
+ in /var/local/upstart\_helpers/:
81
82
 
82
83
  fb-myapp-my_another_tail_cmd.sh
83
84
  fb-myapp-my_tail_cmd.sh
@@ -102,5 +103,4 @@ To remove upstart scripts and helpers for a particular application one can run
102
103
 
103
104
  sudo upstart-export -c -n myapp
104
105
 
105
- The logs will not be cleared.
106
-
106
+ The logs are not cleared in this case. Also, all old application scripts are cleared before each export.
@@ -1,5 +1,5 @@
1
1
  module Upstart
2
2
  class Exporter
3
- VERSION = "0.0.5"
3
+ VERSION = "0.0.6"
4
4
  end
5
5
  end
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: upstart-exporter
3
3
  version: !ruby/object:Gem::Version
4
- hash: 21
4
+ hash: 19
5
5
  prerelease:
6
6
  segments:
7
7
  - 0
8
8
  - 0
9
- - 5
10
- version: 0.0.5
9
+ - 6
10
+ version: 0.0.6
11
11
  platform: ruby
12
12
  authors:
13
13
  - Ilya Averyanov