Skip to content
Browse files

Add concerto-hardware db stuff

  • Loading branch information...
1 parent 4a12ec5 commit 0ab1f517c7202224cb912a3ca81c0eacfd5f49d8 @augustf augustf committed Feb 18, 2014
View
13 db/migrate/20140219024717_create_concerto_hardware_players.hardware.rb
@@ -0,0 +1,13 @@
+# This migration comes from hardware (originally 20121220000000)
+class CreateConcertoHardwarePlayers < ActiveRecord::Migration
+ def change
+ create_table :concerto_hardware_players do |t|
+ t.string :secret
+ t.string :ip_address
+ t.integer :screen_id
+ t.boolean :activated
+
+ t.timestamps
+ end
+ end
+end
View
7 db/migrate/20140219024718_add_updates_to_concerto_hardware_players.hardware.rb
@@ -0,0 +1,7 @@
+# This migration comes from hardware (originally 20131127201048)
+class AddUpdatesToConcertoHardwarePlayers < ActiveRecord::Migration
+ def change
+ remove_column :concerto_hardware_players, :secret
+ add_column :concerto_hardware_players, :screen_on_off, :string
+ end
+end
View
11 db/schema.rb
@@ -11,7 +11,7 @@
#
# It's strongly recommended to check this file into your version control system.
-ActiveRecord::Schema.define(:version => 20131221173425) do
+ActiveRecord::Schema.define(:version => 20140219024718) do
create_table "activities", :force => true do |t|
t.integer "trackable_id"
@@ -47,6 +47,15 @@
add_index "concerto_configs", ["key"], :name => "index_concerto_configs_on_key", :unique => true
+ create_table "concerto_hardware_players", :force => true do |t|
+ t.string "ip_address"
+ t.integer "screen_id"
+ t.boolean "activated"
+ t.datetime "created_at", :null => false
+ t.datetime "updated_at", :null => false
+ t.string "screen_on_off"
+ end
+
create_table "concerto_plugins", :force => true do |t|
t.boolean "enabled"
t.string "gem_name"

3 comments on commit 0ab1f51

@zr2d2
Concerto Digital Signage member
zr2d2 commented on 0ab1f51 Apr 27, 2014

Why are we adding plugin migrations directly to Concerto? Shouldn't migrations be copied in when you install the plugin?

@augustf
Concerto Digital Signage member

This is because we want hardware to be a default plugin, and leaving its migration unresolved created problems with developer workflow.

@zr2d2
Concerto Digital Signage member
zr2d2 commented on 0ab1f51 Apr 27, 2014

Well, they were preventing rake db:migrate from running when I was trying to rebuild my database, so it seems like they may still pose a problem

Please sign in to comment.
Something went wrong with that request. Please try again.