dkdeploy-core 8.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 1917de8366d09d735d45edfb17831902efecef8c
+  data.tar.gz: 82c78217ef34e6b25b9b17c6aba874bb3c0ca0f7
+SHA512:
+  metadata.gz: b5406224374c692372a2633db3d31904774998f9535e21837c27d93cd40056eb26f7a25f61895e0b6221f7a8c651b8b7cd08833e2c2ca30ae713e7616684a5e3
+  data.tar.gz: f3a139321448651327315f2db45416d0e328d255cfd493564f604f70bd74c10a561ec081bb3f2d1b7f914e484884457b1815c9d4d3ffcd0581ae871172a9ba70

data/.gitignore

@@ -0,0 +1,20 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+.rakeTasks
+.vagrant
+.lock
+Gemfile.lock

data/.rubocop.yml

@@ -0,0 +1,18 @@
+AllCops:
+  Exclude:
+    - 'tmp/**/*'
+    - 'spec/fixtures/application/htdocs/stylesheets/**/config.rb'
+    - 'config/**/*'
+    - 'Vagrantfile'
+GlobalVars:
+  AllowedVariables: []
+MethodLength:
+  Max: 25
+LineLength:
+  Max: 200
+SpecialGlobalVars:
+  Enabled: false
+BracesAroundHashParameters:
+  Enabled: false
+CyclomaticComplexity:
+  Max: 10

data/Berksfile

@@ -0,0 +1,3 @@
+source 'https://supermarket.chef.io'
+
+cookbook 'dkdeploy-core', path: 'config/vm/cookbooks/dkdeploy-core'

data/Berksfile.lock

@@ -0,0 +1,46 @@
+DEPENDENCIES
+  dkdeploy-core
+    path: config/vm/cookbooks/dkdeploy-core
+
+GRAPH
+  7-zip (1.0.2)
+    windows (>= 1.2.2)
+  apt (2.9.2)
+  build-essential (2.3.1)
+    7-zip (>= 0.0.0)
+  chef-sugar (3.3.0)
+  chef_handler (1.3.0)
+  database (4.0.9)
+    postgresql (>= 1.0.0)
+  dkdeploy-core (1.0.0)
+    apt (~> 2.9)
+    database (~> 4.0)
+    mysql (~> 6.0)
+    mysql2_chef_gem (~> 1.0)
+  mariadb (0.3.1)
+    apt (>= 0.0.0)
+    yum (>= 0.0.0)
+    yum-epel (>= 0.0.0)
+  mysql (6.1.2)
+    smf (>= 0.0.0)
+    yum-mysql-community (>= 0.0.0)
+  mysql2_chef_gem (1.0.2)
+    build-essential (>= 0.0.0)
+    mariadb (>= 0.0.0)
+    mysql (~> 6.0)
+  openssl (4.4.0)
+    chef-sugar (>= 3.1.1)
+  postgresql (4.0.0)
+    apt (>= 1.9.0)
+    build-essential (>= 0.0.0)
+    openssl (~> 4.0)
+  rbac (1.0.3)
+  smf (2.2.8)
+    rbac (>= 1.0.1)
+  windows (1.39.1)
+    chef_handler (>= 0.0.0)
+  yum (3.10.0)
+  yum-epel (0.6.5)
+    yum (~> 3.2)
+  yum-mysql-community (0.1.21)
+    yum (>= 3.2)

data/CONTRIBUTORS.md

@@ -0,0 +1,16 @@
+# dkdeploy CONTRIBUTORS
+
+The dkdeploy core maintainers would like to recognize following contributors (in alphabetic order):
+
+- Sascha Egerer
+- Christoph Gerold
+- Johannes Goslar
+- Kieran Hayes
+- Wilfried Irßlinger
+- Thomas Jahnke
+- Gleb Levitin
+- Luka Lüdicke
+- Nicolai Reuschling
+- Lars Tode
+- Timo Webler
+- Mike Zaschka

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org/'
+
+# Specify your gem's dependencies in dkdeploy-core.gemspec
+gemspec

data/LICENSE

@@ -0,0 +1,7 @@
+Copyright (c) 2014-2016 dkd Internet Service GmbH, Frankfurt am Main (Germany), https://dkd.de/
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,88 @@
+# Dkdeploy::Core
+
+[![Gem Version](https://badge.fury.io/rb/dkdeploy-core.svg)](https://badge.fury.io/rb/dkdeploy-core)
+
+## Description
+
+This Rubygem `dkdeploy-core` represents the extension of [Capistrano](http://capistranorb.com/) tasks directed to advanced deployment processes.
+
+## Installation
+
+Add this line to your application's `Gemfile`
+
+	gem 'dkdeploy-core', '~> 8.0'
+
+and then execute
+
+	bundle install
+
+or install it yourself as
+
+	gem install dkdeploy-core
+
+## Usage
+
+Run in your project root
+
+	cap install STAGES='dev,integration,testing,production'
+
+This command will create the following Capistrano file structure with all the standard pre-configured constants.
+Please be aware of the difference to the [native installation](http://capistranorb.com/documentation/getting-started/preparing-your-application/) of Capistrano.
+Certainly you have to adjust `config/deploy.rb` and respective stages and customize them for your needs.
+
+<pre>
+  ├── Capfile
+  └── config
+     ├── deploy
+     │   ├── dev.rb
+     │   ├── integration.rb
+     │   ├── testing.rb
+     │   └── production.rb
+     └── deploy.rb
+</pre>
+
+As next you have to append the following line to the `Capfile` in order to make use of dkdeploy extensions in addition to the standard Capistrano tasks:
+
+	require 'capistrano/dkdeploy/core'
+
+To convince yourself, that Capistrano tasks list has been extended, please run
+
+	cap -vT
+
+Please note, that dkdeploy uses the local copy strategy and overwrites the `:scm` constant. If you want to use it,
+you should do nothing more. However if you want to change it, for example to `:git`, please add the following line to `deploy.rb`
+
+	set :scm, :git
+
+For more information about available Capistrano constants please use the [Capistrano documentation](http://capistranorb.com/documentation/getting-started/preparing-your-application/).
+The complete list of the dkdeploy constants you find in `/lib/capistrano/dkdeploy/core.rb`.
+
+## Testing
+
+### Prerequisite
+
+rvm (v1.25.x) with installed Ruby 2.1.
+
+Add the virtual box alias to your `hosts` file
+
+	192.168.156.180 dkdeploy-core.dev
+
+### Running tests
+
+1. Starting the local box (`vagrant up --provision`)
+2. Checking coding styles (`rubocop`)
+3. Running BDD cucumber tests (`cucumber`)
+
+## Contributing
+
+1. Install [git flow](https://github.com/nvie/gitflow)
+2. Install [Homebrew](http://brew.sh/) and run `brew install mysql-connector-c`
+3. Install [NodeJS](https://nodejs.org) (supported: v0.12.7) via `brew install nodejs`
+4. Install [Bower](http://bower.io) (supported: v1.7.9) via `npm install -g bower@1.7.9`
+5. If project is not checked out already do git clone `git@github.com:dkdeploy/dkdeploy-core.git`
+6. Checkout origin develop branch (`git checkout --track -b develop origin/develop`)
+7. Git flow initialze `git flow init -d`
+8. Installing gems `bundle install`
+9. Create new feature branch (`git flow feature start my-new-feature`)
+10. Run tests (README.md Testing)
+11. Commit your changes (`git commit -am 'Add some feature'`)

data/Rakefile

@@ -0,0 +1,5 @@
+task default: :spec
+require 'bundler/gem_tasks'
+
+require 'rspec/core/rake_task'
+RSpec::Core::RakeTask.new

data/Vagrantfile

@@ -0,0 +1,60 @@
+unless Vagrant.has_plugin?('vagrant-berkshelf')
+  puts "Please install vagrant plugin vagrant-berkshelfs first\n"
+  puts " vagrant plugin install vagrant-berkshelf\n\n"
+  puts "Exit vagrant\n\n"
+  abort
+end
+
+unless Vagrant.has_plugin?('vagrant-omnibus')
+  puts "Please install vagrant plugin vagrant-omnibus first\n"
+  puts " vagrant plugin install vagrant-omnibus\n\n"
+  puts "Exit vagrant\n\n"
+  abort
+end
+
+Vagrant.require_version '~> 1.8.1'
+chef_version = '12.9.41'
+
+Vagrant.configure(2) do |config|
+  domain = 'dkdeploy-core.dev'
+  ip_address = '192.168.156.180'
+
+  # Search boxes at https://atlas.hashicorp.com/search.
+  config.vm.box = 'ubuntu/trusty64'
+  config.vm.box_check_update = false
+  config.berkshelf.enabled = true
+  config.omnibus.chef_version = chef_version
+
+  config.vm.define('dkdeploy-core', primary: true) do |master_config|
+    master_config.vm.network 'private_network', ip: ip_address
+
+    # Chef settings
+    master_config.vm.provision :chef_solo do |chef|
+      chef.version = chef_version
+      chef.install = false # omnibus does it already
+      chef.log_level = :info
+      chef.add_recipe 'dkdeploy-core'
+    end
+
+    # Memory limit and name of Virtualbox
+    master_config.vm.provider 'virtualbox' do |virtualbox|
+      virtualbox.name = domain
+      virtualbox.gui = ENV['ENABLE_GUI_MODE'] && ENV['ENABLE_GUI_MODE'] =~ /^(true|yes|y|1)$/i
+      virtualbox.customize [
+                              'modifyvm', :id,
+                              '--natdnsproxy1', 'off',
+                              '--natdnshostresolver1', 'on',
+                              '--memory', '1024'
+                           ]
+    end
+  end
+
+  if Vagrant.has_plugin?('landrush')
+    config.landrush.enabled = true
+    config.landrush.guest_redirect_dns = false
+    config.landrush.tld = 'dev'
+    config.landrush.host domain, ip_address
+  else
+    config.vm.post_up_message = "Either install Vagrant plugin 'landrush' or add this entry to your host file: #{ip_address} #{domain}"
+  end
+end

data/config/vm/cookbooks/dkdeploy-core/metadata.rb

@@ -0,0 +1,10 @@
+name 'dkdeploy-core'
+maintainer 'dkd Internet Service GmbH'
+license 'MIT'
+description 'Project cookbook'
+version '1.0.0'
+
+depends 'mysql', '~> 6.0'
+depends 'mysql2_chef_gem', '~> 1.0'
+depends 'database', '~> 4.0'
+depends 'apt', '~> 2.9'

data/config/vm/cookbooks/dkdeploy-core/recipes/default.rb

@@ -0,0 +1,56 @@
+# update apt packages
+include_recipe 'apt'
+
+# Create unix user for tests
+user 'test-user' do
+  action :create
+end
+
+group 'test-group' do
+  action :create
+  append true
+  members 'test-user'
+end
+
+# install apache2-utils. It is needed for the assets:add_htpasswd task
+package 'apache2-utils' do
+  action :install
+end
+
+mysql_service 'default' do
+  port '3306'
+  # Need for remote connection
+  bind_address '0.0.0.0'
+  action [:create, :start]
+end
+
+mysql2_chef_gem 'default' do
+  action :install
+end
+
+mysql_connection_info = {
+  :host     => '127.0.0.1',
+  :username => 'root',
+  :password => 'ilikerandompasswords'
+}
+
+mysql_database 'dkdeploy_core' do
+  connection mysql_connection_info
+  action   :create
+end
+
+mysql_database_user 'root' do
+  connection mysql_connection_info
+  host       '%'
+  password   'ilikerandompasswords'
+  action     :create
+  privileges [:all]
+  action     :grant
+end
+
+directory '/var/www' do
+  owner 'vagrant'
+  owner 'vagrant'
+  mode '0770'
+  action :create
+end

data/dkdeploy-core.gemspec

@@ -0,0 +1,34 @@
+# coding: utf-8
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'dkdeploy/core/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = 'dkdeploy-core'
+  spec.version       = Dkdeploy::Core::Version
+  spec.license       = 'MIT'
+  spec.authors       = ['Lars Tode', 'Timo Webler', 'Kieran Hayes', 'Nicolai Reuschling', 'Johannes Goslar', 'Luka Lüdicke']
+  spec.email         = %w(lars.tode@dkd.de timo.webler@dkd.de kieran.hayes@dkd.de nicolai.reuschling@dkd.de johannes.goslar@dkd.de luka.luedicke@dkd.de)
+  spec.description   = 'dkd basic deployment tasks and strategies'
+  spec.summary       = 'dkd basic deployment tasks and strategies'
+  spec.homepage      = 'https://redmine.dkd.de/projects/dkdeploy/wiki'
+
+  spec.files         = `git ls-files`.split($/)
+  spec.executables   = spec.files.grep(%r{^bin\/}) { |f| File.basename(f) }
+  spec.test_files    = spec.files.grep(%r{^(test|spec|features)\/})
+  spec.require_paths = ['lib']
+
+  spec.add_development_dependency 'bundler', '~> 1.12.5'
+  spec.add_development_dependency 'rake', '~> 11.2'
+  spec.add_development_dependency 'rspec', '~> 3.4'
+  spec.add_development_dependency 'cucumber', '~> 2.4'
+  spec.add_development_dependency 'rubocop', '~> 0.40'
+  spec.add_development_dependency 'aruba', '~> 0.14.1'
+  spec.add_development_dependency 'mysql2', '~> 0.3'
+  spec.add_development_dependency 'pry', '~> 0.10.3'
+  spec.add_development_dependency 'dkdeploy-test_environment', '~> 1.0'
+
+  spec.add_dependency 'capistrano', '~> 3.5.0'
+  spec.add_dependency 'sshkit', '= 1.10.0'
+  spec.add_dependency 'highline', '~> 1.7.1'
+end

data/features/apache.feature

@@ -0,0 +1,35 @@
+Feature: Test tasks for namespace 'apache'
+
+	Background:
+		Given a test app with the default configuration
+
+	Scenario: copy only a local .htaccess file into web root (there is no other stage specific .htaccess file available)
+		When I remove the file "config/etc/apache2/conf/dev.htaccess.erb"
+		And I successfully run `cap dev apache:htaccess`
+		Then a file named "htdocs/.htaccess" should exist
+		And the file "htdocs/.htaccess" should contain exactly:
+		"""
+		<FilesMatch "index.php">
+		Allow from all
+		</FilesMatch>
+
+		"""
+
+	Scenario: copy a local .htaccess file into web root and merge it with dev.htacces
+		When I successfully run `cap dev apache:htaccess`
+		Then a file named "htdocs/.htaccess" should exist
+		And the file "htdocs/.htaccess" should contain exactly:
+		"""
+		<FilesMatch "index.php">
+		Allow from all
+		</FilesMatch>
+		<Files "favicon.ico">
+		Deny from all
+		</Files>
+		"""
+
+	Scenario: change web root and copy a local .htaccess file into it
+		Given a directory named "web_root"
+		When I extend the development capistrano configuration variable local_web_root_path with value 'web_root'
+		And I successfully run `cap dev apache:htaccess`
+		Then a file named "web_root/.htaccess" should exist

data/features/assets.feature

@@ -0,0 +1,100 @@
+Feature: Test tasks for namespace 'assets'
+
+	Background:
+		Given a test app with the default configuration
+
+	Scenario: Check if compass files are compiled into the configured folder
+		Given the remote server is cleared
+		And the project is deployed
+		And I extend the development capistrano configuration from the fixture file custom_compass_sources.rb
+		When I successfully run `cap dev assets:compile_compass`
+		Then a file named "htdocs/stylesheets/test1/css/source.css" should exist
+		And a file named "htdocs/stylesheets/test2/css/source.css" should exist
+
+	Scenario: Check if compass files are compiled given by command line
+		Given the remote server is cleared
+		And the project is deployed
+		When I successfully run `cap dev "assets:compile_compass['htdocs/stylesheets/test1']"`
+		Then a file named "htdocs/stylesheets/test1/css/source.css" should exist
+
+	Scenario: Check if compass files are compiled given by command line with arguments
+		Given the remote server is cleared
+		And the project is deployed
+		When I successfully run `cap dev "assets:compile_compass['htdocs/stylesheets/test1','--boring']"`
+		Then a file named "htdocs/stylesheets/test1/css/source.css" should exist
+		And the output should contain "--boring"
+
+	Scenario: Check if compass files are compiled with pre defined arguments
+		Given the remote server is cleared
+		And the project is deployed
+		And I extend the development capistrano configuration variable compass_compile_arguments with value ['--boring', '--environment', 'production']
+		When I successfully run `cap dev "assets:compile_compass['htdocs/stylesheets/test1']"`
+		Then a file named "htdocs/stylesheets/test1/css/source.css" should exist
+		And the output should contain "--boring"
+
+	Scenario: Check if the htpasswd file is created with the correct data
+		Given the remote server is cleared
+		And I run `cap dev assets:add_htpasswd` interactively
+		And I type "dkd_test_user"
+		And I type "dkd_test_password"
+		And I close the stdin stream
+		Then the exit status should be 0
+		And a remote file named "shared_path/.htpasswd" should exist
+
+	Scenario: Check if cleanup is really cleaning fileadmin and uploads
+		Given the remote server is cleared
+		And the project is deployed
+		When I successfully run `cap dev assets:cleanup`
+		Given a remote empty file named "assets_path/fileadmin/example.png"
+		Then a remote file named "assets_path/fileadmin/example.png" should exist
+		When I successfully run `cap dev assets:cleanup`
+		Then a remote file named "assets_path/fileadmin/example.png" should not exist
+
+	Scenario: Check if download is getting archives from the remote server
+		Given the remote server is cleared
+		And the project is deployed
+		When I successfully run `cap dev assets:cleanup`
+		Given a remote empty file named "assets_path/fileadmin/example.png"
+		And a remote empty file named "assets_path/fileadmin/folder/example3.png"
+		And a remote empty file named "assets_path/uploads/example3.png"
+		When I run `cap dev assets:download`
+		Then a file named "temp/assets/uploads.tar.gz" should exist
+		And a file named "temp/assets/fileadmin.tar.gz" should exist
+
+	Scenario: Check if update is filling the remote server from the local archives
+		Given the remote server is cleared
+		And the project is deployed
+		When I successfully run `cap dev assets:cleanup`
+		Given a remote empty file named "assets_path/fileadmin/file.html"
+		And a remote empty file named "assets_path/uploads/subdirectory/file2.html"
+		And a remote empty file named "assets_path/uploads/file3.html"
+		When I successfully run `cap dev assets:download`
+		And I successfully run `cap dev assets:cleanup`
+		Then a remote file named "assets_path/fileadmin/file.html" should not exist
+		And a remote file named "assets_path/uploads/subdirectory/file2.html" should not exist
+		And a remote file named "assets_path/uploads/file3.html" should not exist
+		When I successfully run `cap dev assets:update`
+		And a remote file named "assets_path/fileadmin/file.html" should exist
+		And a remote file named "assets_path/uploads/subdirectory/file2.html" should exist
+		And a remote file named "assets_path/uploads/file3.html" should exist
+
+	Scenario: Check if add_default_content is filling the remote server from the local preseeds
+		Given the remote server is cleared
+		And the project is deployed
+		When I successfully run `cap dev assets:cleanup`
+		And I successfully run `cap dev assets:add_default_content`
+		Then a remote file named "assets_path/fileadmin/file1.html" should exist
+		And a remote file named "assets_path/fileadmin/subdirectory/file2.html" should exist
+		And a remote file named "assets_path/uploads/test.png" should exist
+
+	Scenario: Check if the exclude file is functioning
+		Given the remote server is cleared
+		And the project is deployed
+		When I successfully run `cap dev assets:cleanup`
+		Given a remote empty file named "assets_path/fileadmin/should_be_excluded.txt"
+		Then a remote file named "assets_path/fileadmin/should_be_excluded.txt" should exist
+		When I successfully run `cap dev assets:download`
+		And I successfully run `cap dev assets:cleanup`
+		Then a remote file named "assets_path/fileadmin/should_be_excluded.txt" should not exist
+		When I successfully run `cap dev assets:update`
+		Then a remote file named "assets_path/fileadmin/should_be_excluded.txt" should not exist