oye 0.1.11 → 0.1.12
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/Gemfile.lock +2 -2
- data/README.md +12 -0
- data/lib/oye/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: a0f6ff207c4fac96695688a50e1b59a630d00d0da82f2b467d8e887a4a4f147c
|
4
|
+
data.tar.gz: '043181a7f859c284c01e8f37c9ca55f447e21a256e7e0b3f6c6d6bc1f4736e28'
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 7bba790ca065eb5b4ea379a28490ac02e80a63e3998582c0037733a31ad3b0496ef073e695f66d5157e452448526a72da44be0ec5f9ff6def5e1d91a4fa6d7f0
|
7
|
+
data.tar.gz: 4a4914bd17c72fb35875230f3e651b4db0109b07a9a21a781660ec7769012577794170792d225e12d24cc142fe19d52d30705a40e3b6dd4e4621d6c65b4667c6
|
data/Gemfile.lock
CHANGED
data/README.md
CHANGED
@@ -10,10 +10,22 @@ A continuous monitoring tool that does a few things:
|
|
10
10
|
[ ] run rails tests inside Oye.monitor
|
11
11
|
[ ] check for irregularities in @repos, e.g two repeated cloned repos
|
12
12
|
[ ] give warning if port is not open by using `port_open?` method
|
13
|
+
- fix possible port conflicts. for example `oye -p 3000` will add that port to the list of ports (or sockets) already specified in the app's config file (unicorn.rb). but you print an error if there are port conflicts
|
13
14
|
[ ] why is the trap with `FileUtils.rm_f(oye_pidfile)` not removing the PID file
|
14
15
|
[ ] make a website for 'oye' where you provide better documentation. e.g.
|
15
16
|
- how to set up oye.yml
|
16
17
|
[ ] create a git brach called 'oye' and pull from that one instead of 'origin'.
|
17
18
|
[ ] suport remote branches via 'ssh'. e.g. you can use `Net::SSH` as i use in '~/.ruby/req'
|
19
|
+
[ ] support for webrick app server
|
20
|
+
[ ] support for apps that dont use an app server (e.g. oye.dance and sergioro.mx run in nginx alone)
|
18
21
|
[ ] support 'jekyll serve' for people that dont want to use a web server for jekyll
|
19
22
|
[ ] split the file. use Oye::Actions as a namespace for update, restart, start, stop methods
|
23
|
+
[ ] read environment for each app from oye.yml. e.g. user cn specify 'production' for one app and 'development' for another. The '-e' option is the default environment to be used if none is specified in oye.yml
|
24
|
+
[ ] change %x() to system() to prevent undesired prints to console (e.g. if you stop 'oye' while it is running '%x(bundler)' it will dump bundler errors to the console.)
|
25
|
+
[ ] give specific help for each command like jekyl does `jekyll [cmd] -h`
|
26
|
+
- e.g. with `oye port -h`
|
27
|
+
[ ] there might be a hard-to-find-bug if `oye` is executing a `git pull` while the origin repo is receiving data from a `git push`.
|
28
|
+
[ ] in 'oye.yml' you could pass an aditional parameter to specify what type of app it is. in this way you dont need to use `is_rails?`. e.g.
|
29
|
+
/git/pete.land.git:
|
30
|
+
- /var/www/html/pete.land:
|
31
|
+
type: jekyll
|
data/lib/oye/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: oye
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.1.
|
4
|
+
version: 0.1.12
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- sergioro
|
8
8
|
autorequire:
|
9
9
|
bindir: exe
|
10
10
|
cert_chain: []
|
11
|
-
date: 2020-05-
|
11
|
+
date: 2020-05-27 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: benchmark-ips
|