rsync-deploy 0.0.16 → 0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 3717284c1b26d927d0e36696e2539e5964165f75
-  data.tar.gz: df5757be4cec9ed087d0b3295d187aadb6b9c856
+  metadata.gz: d7099df327d321811dbc7056ecf72b193192b8f6
+  data.tar.gz: 20ae2c3b2bbf1efc270f990435d868f1c2725c81
 SHA512:
-  metadata.gz: 9856b050bbfa3c7f53b0203428d77467054f772ee28772ff2be04314c9cf9b3a9456d395c6edc56c51cc6a153b50c659327f291554eb2c1a5bb0adbd700b5a1a
-  data.tar.gz: 3159216a6de8b0d6d451080b8f866e318d96a92e0b14d7060f0339fe1780e164ac102ffd9bf28d0a631bfdfe2d044971ce230c561394a636a15b1b3d74363521
+  metadata.gz: adbd2c994dd599b7d93e63e36a6136134971cb9380f7fdc0a261583b2c94c4a7889d0b0fbae8c8b5515a500ea52f6ebe1d65b0f459dbae1b092071a163d71e48
+  data.tar.gz: 085119d2dbc794f42fb42c92bc98142180341fa9ceea5bd0e483accd4c5b1245003721fa4ae43b7c7eae1bd7b06f514efd62725345fc4e52f0c4e0f97b643e03

data/.gitignore

@@ -15,4 +15,5 @@ spec/reports
 test/tmp
 test/version_tmp
 tmp
-.DS_Store
+.DS_Store
+resources/

data/README.md

@@ -23,13 +23,16 @@ This will create a `deploy.yml` file that controls how the deployment should tak
 Fill in your server details. For example:
 
 ```
-# Server
 server_name:
     host: "server.com"
     user: "user"
+    sync: true
     path:
         local: "deploy/"
         remote: "www/"
+    exclude: 
+        - ".DS_Store"
+        - "resources/"
 ```
 
 Once your `deploy.yml` is set up, simply deploy by running:
@@ -60,7 +63,7 @@ deploy dev staging production
 
 #### deploy download [env...]
 
-Will download from the environment(s) listed. This works in reverse, so files from `path.remote` will go into `path.local`
+Will download from the environment(s) listed. This works in reverse, so files from `path.remote` will go into `path.local`. This will never delete files that aren't on the server, but will likely overwrite your local copies, so be careful.
 
 This command is also aliased as `down` and `d`, so it can be run like:
 
@@ -79,7 +82,7 @@ Will change the name of deployment configuration files. By default they are name
 
 #### deploy help
 
-Will output a list of all commands
+Will output a list of all commands.
 
 
 ## Config
@@ -217,6 +220,23 @@ deploy staging production
 
 If you don't specify an environment, it's assumed that the first environment in `deploy.yml` should be used. So, with the above configuration, running `deploy` would upload to `staging` by default.
 
+## Autocompletion
+
+To enable tab-completion based for commands and the current directory's environments, put in your `~/.bash_profile` the following code:
+
+```
+# Add tab completion for `deploy` configurations in current directory
+_dply()
+{
+  local cur=${COMP_WORDS[COMP_CWORD]}
+  local file=$(cat $(ruby -e "puts Gem::Specification.find_by_name('rsync-deploy').gem_dir + '/lib/config.yml'") | awk '{print $2}')
+  if [ -f $file ]; then
+    ENVS=$(ls $PWD | grep ":$" $file | sed '/^  /d' | tr -d ':')
+  fi
+  COMPREPLY=($(compgen -W "${ENVS} install config list help version" -- $cur))
+}
+complete -o "default" -F _dply deploy
+```
 
 ## Mentions
 

data/bin/deploy

@@ -1,7 +1,6 @@
 #!/usr/bin/env ruby
 
 require 'deploy'
-require 'fileutils'
 
 # TODO: Allow creation of environments from install command, for example
 # `deploy install live dev` would create a file with live and dev
@@ -142,6 +141,5 @@ when 'config'
 	exit
 end
 
-
 # Run the deploy straight if nothing else triggered
 go(false)

data/lib/deploy/version.rb

@@ -1,5 +1,5 @@
 module Deploy
   
-  VERSION = "0.0.16"
+  VERSION = "0.1.0"
   
 end

data/lib/deploy.rb

@@ -68,7 +68,7 @@ module Deploy
       end
       
     end
-
+    
   end
 
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rsync-deploy
 version: !ruby/object:Gem::Version
-  version: 0.0.16
+  version: 0.1.0
 platform: ruby
 authors:
 - Ross Zurowski