Fix is_active migration (#144)

* Do a proper change default migration.

* Restore deleted migration.

* Renamed new migration so it is run at the same point in time.

* Update schema.

* Run deployment from this branch to fix migrations.

* Use db schema from dev.

* Run deployment from dev, not from this branch.

Author: WorldofJARcraft

…/20191129151616_add_is_active_to_poll.rb …/20191204101435_add_is_active_to_poll.rbdb/migrate/20191129151616_add_is_active_to_poll.rb renamed to db/migrate/20191204101435_add_is_active_to_poll.rb db/migrate/20191129151616_add_is_active_to_poll.rb renamed to db/migrate/20191204101435_add_is_active_to_poll.rb

@@ -1,5 +1,5 @@
 class AddIsActiveToPoll < ActiveRecord::Migration[5.2]
   def change
-    add_column :polls, :is_active, :boolean, null: false, default: true
+    add_column :polls, :is_active, :boolean, null: false, default: false
   end
 end

db/migrate/20191204101436_change_is_active_default.rb

@@ -0,0 +1,5 @@
+class ChangeIsActiveDefault < ActiveRecord::Migration[5.2]
+  def change
+    change_column_default :polls, :is_active, true
+  end
+end

deployment.sh

@@ -5,6 +5,7 @@ then
 elif [ "$TRAVIS_BRANCH" = "dev" ]
 then 
 	export APP="hpi-lectureportal-dev"; 
+	export APP="hpi-lectureportal-dev";
 else
 	echo "No deployment on branch $TRAVIS_BRANCH";
 	exit 0
@@ -21,4 +22,4 @@ then
 else
   echo "Docker build failed!"
   exit 1
-fi
+fi