rbbt-image 0.1.10 → 0.1.11

Sign up to get free protection for your applications and to get access to all the features.
Files changed (4) hide show
  1. checksums.yaml +4 -4
  2. data/Dockerfile +6 -0
  3. data/Vagrantfile +136 -0
  4. metadata +4 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 4315b3197e42bc7bc251c929639ba3305a94b05e
4
- data.tar.gz: 850d49ad2942e9fc5ca9d30a196145dffd12bcf5
3
+ metadata.gz: 7431088bb3c94a21cf7a1925f92df9c81a524148
4
+ data.tar.gz: e47907509e014ffad5202ed69529379450816a44
5
5
  SHA512:
6
- metadata.gz: 3b6b9dfc32521fc1c23074129d13d8f0b9e5c89c1d38440d24d01533d245439e50bc1adb0480fd1171e2d9593094abbbd418210a871c8e6141e37379d64e713a
7
- data.tar.gz: ff3cee902de1d1296c991f67fef69c7447a0e8d970cadac8bb60f1c2c096e0a5d9e6dd48a913692fdc75c5ab05589bc9e1ba7f87ca44e6497a4e500c0dc859c6
6
+ metadata.gz: 4774b4345c4d40da549c8b02ec082e96d998084b71d62306394ecf295b6b857f5fc70ca7eff8837b6503117a6bcd03a023b5691be01d21e096a440d4e772b84a
7
+ data.tar.gz: c8a9c7ac6168d843340ee620d0d4c69db0018bfe2303adefc2a974dbee46dd36d20cb9c9c37c06d7636fc50d7657197cc7eb96be9e7171c8df042cb0f232ab59
data/Dockerfile ADDED
@@ -0,0 +1,6 @@
1
+ FROM ubuntu
2
+ USER root
3
+ ADD provision.sh /tmp/provision.sh
4
+ RUN /bin/bash /tmp/provision.sh
5
+ USER rbbt
6
+ ENV HOME /home/rbbt
data/Vagrantfile ADDED
@@ -0,0 +1,136 @@
1
+ # -*- mode: ruby -*-
2
+ # vi: set ft=ruby :
3
+
4
+ build_script = File.join(File.basename(__FILE__), 'bin/build_rbbt_provision_sh')
5
+ provision_script = `ruby #{build_script}`
6
+
7
+ VAGRANTFILE_API_VERSION = "2"
8
+
9
+ Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
10
+ # All Vagrant configuration is done here. The most common configuration
11
+ # options are documented and commented below. For a complete reference,
12
+ # please see the online documentation at vagrantup.com.
13
+
14
+ # Every Vagrant virtual environment requires a box to build off of.
15
+ config.vm.box = "precise32"
16
+
17
+ # The url from where the 'config.vm.box' box will be fetched if it
18
+ # doesn't already exist on the user's system.
19
+ config.vm.box_url = "http://files.vagrantup.com/precise32.box"
20
+
21
+ config.vm.network "forwarded_port", guest: 2887, host: 28879
22
+
23
+ config.vm.provision :shell, :inline => provision_script
24
+
25
+ # Create a forwarded port mapping which allows access to a specific port
26
+ # within the machine from a port on the host machine. In the example below,
27
+ # accessing "localhost:8080" will access port 80 on the guest machine.
28
+ # config.vm.network :forwarded_port, guest: 80, host: 8080
29
+
30
+ # Create a private network, which allows host-only access to the machine
31
+ # using a specific IP.
32
+ # config.vm.network :private_network, ip: "192.168.33.10"
33
+
34
+ # Create a public network, which generally matched to bridged network.
35
+ # Bridged networks make the machine appear as another physical device on
36
+ # your network.
37
+ # config.vm.network :public_network
38
+
39
+ # If true, then any SSH connections made will enable agent forwarding.
40
+ # Default value: false
41
+ # config.ssh.forward_agent = true
42
+
43
+ # Share an additional folder to the guest VM. The first argument is
44
+ # the path on the host to the actual folder. The second argument is
45
+ # the path on the guest to mount the folder. And the optional third
46
+ # argument is a set of non-required options.
47
+ # config.vm.synced_folder "../data", "/vagrant_data"
48
+
49
+ # Provider-specific configuration so you can fine-tune various
50
+ # backing providers for Vagrant. These expose provider-specific options.
51
+ # Example for VirtualBox:
52
+ #
53
+ #
54
+
55
+ Vagrant.configure("2") do |config|
56
+ config.vm.provider "docker" do |d|
57
+ d.image = "ubuntu:14.04.2"
58
+ end
59
+ end
60
+ #
61
+ # config.vm.provider :virtualbox do |vb|
62
+ # # Don't boot with headless mode
63
+ # vb.gui = true
64
+ #
65
+ # # Use VBoxManage to customize the VM. For example to change memory:
66
+ # vb.customize ["modifyvm", :id, "--memory", "1024"]
67
+ # end
68
+ #
69
+ # View the documentation for the provider you're using for more
70
+ # information on available options.
71
+
72
+ # Enable provisioning with Puppet stand alone. Puppet manifests
73
+ # are contained in a directory path relative to this Vagrantfile.
74
+ # You will need to create the manifests directory and a manifest in
75
+ # the file precise32.pp in the manifests_path directory.
76
+ #
77
+ # An example Puppet manifest to provision the message of the day:
78
+ #
79
+ # # group { "puppet":
80
+ # # ensure => "present",
81
+ # # }
82
+ # #
83
+ # # File { owner => 0, group => 0, mode => 0644 }
84
+ # #
85
+ # # file { '/etc/motd':
86
+ # # content => "Welcome to your Vagrant-built virtual machine!
87
+ # # Managed by Puppet.\n"
88
+ # # }
89
+ #
90
+ # config.vm.provision :puppet do |puppet|
91
+ # puppet.manifests_path = "manifests"
92
+ # puppet.manifest_file = "site.pp"
93
+ # end
94
+
95
+ # Enable provisioning with chef solo, specifying a cookbooks path, roles
96
+ # path, and data_bags path (all relative to this Vagrantfile), and adding
97
+ # some recipes and/or roles.
98
+ #
99
+ # config.vm.provision :chef_solo do |chef|
100
+ # chef.cookbooks_path = "../my-recipes/cookbooks"
101
+ # chef.roles_path = "../my-recipes/roles"
102
+ # chef.data_bags_path = "../my-recipes/data_bags"
103
+ # chef.add_recipe "mysql"
104
+ # chef.add_role "web"
105
+ #
106
+ # # You may also specify custom JSON attributes:
107
+ # chef.json = { :mysql_password => "foo" }
108
+ # end
109
+
110
+ # Enable provisioning with chef server, specifying the chef server URL,
111
+ # and the path to the validation key (relative to this Vagrantfile).
112
+ #
113
+ # The Opscode Platform uses HTTPS. Substitute your organization for
114
+ # ORGNAME in the URL and validation key.
115
+ #
116
+ # If you have your own Chef Server, use the appropriate URL, which may be
117
+ # HTTP instead of HTTPS depending on your configuration. Also change the
118
+ # validation key to validation.pem.
119
+ #
120
+ # config.vm.provision :chef_client do |chef|
121
+ # chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
122
+ # chef.validation_key_path = "ORGNAME-validator.pem"
123
+ # end
124
+ #
125
+ # If you're using the Opscode platform, your validator client is
126
+ # ORGNAME-validator, replacing ORGNAME with your organization name.
127
+ #
128
+ # If you have your own Chef Server, the default validation client name is
129
+ # chef-validator, unless you changed the configuration.
130
+ #
131
+ # chef.validation_client_name = "ORGNAME-validator"
132
+ end
133
+
134
+ Vagrant::Config.run do |config|
135
+ config.vm.customize ["modifyvm", :id, "--memory", 1024]
136
+ end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: rbbt-image
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.10
4
+ version: 0.1.11
5
5
  platform: ruby
6
6
  authors:
7
7
  - Miguel Vazquez
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2016-05-19 00:00:00.000000000 Z
11
+ date: 2016-06-13 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: rbbt-util
@@ -33,7 +33,9 @@ extensions: []
33
33
  extra_rdoc_files:
34
34
  - README.md
35
35
  files:
36
+ - Dockerfile
36
37
  - README.md
38
+ - Vagrantfile
37
39
  - bin/build_rbbt_provision_sh.rb
38
40
  - bin/run_rbbt_docker.rb
39
41
  - lib/.keep