Commit b42b5e2f authored by Bob Van Landuyt's avatar Bob Van Landuyt
Browse files

Add `Term` model to keep track of terms

That way we can link a users acceptance of terms directly to a terms record.
parent 109333771a8c
class ApplicationSetting
class Term < ActiveRecord::Base
validates :terms, presence: true
= form_for @application_setting, url: admin_application_settings_path, html: { class: 'form-horizontal fieldset-form' } do |f|
= form_errors(@application_setting)
= f.label :enforce_terms do
= f.check_box :enforce_terms
= _("Require all users to accept Terms of Service when they access GitLab.")
When enabled, users cannot use GitLab until the terms have been accepted.
= f.label :terms do
= _("Terms of Service Agreement")
= f.text_area :terms, class: 'form-control', rows: 8
Markdown enabled
= f.submit 'Save changes', class: "btn btn-success"
class CreateApplicationSettingTerms < ActiveRecord::Migration
include Gitlab::Database::MigrationHelpers
DOWNTIME = false
def change
create_table :application_setting_terms do |t|
t.integer :cached_markdown_version
t.text :terms, null: false
t.text :terms_html
......@@ -40,6 +40,12 @@
t.text "new_project_guidelines_html"
create_table "application_setting_terms", force: :cascade do |t|
t.integer "cached_markdown_version"
t.text "terms", null: false
t.text "terms_html"
create_table "application_settings", force: :cascade do |t|
t.integer "default_projects_limit"
t.boolean "signup_enabled"
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment