In order to ensure compatibility with existing CONSUL installations, we disabled all settings related to SDG. However, we also made it much harder to enable SDG globally on the site, since administrators first had to enable the SDG feature and then enable it for each process. Most people will expect SDG is enabled for all processes once they enable the SDG feature, so that's what we're doing. They can of course disable specific processes should they wish to do so.
29 lines
927 B
Ruby
29 lines
927 B
Ruby
section "Creating Settings" do
|
|
Setting.reset_defaults
|
|
|
|
{
|
|
"facebook_handle": "CONSUL",
|
|
"feature.featured_proposals": "true",
|
|
"feature.map": "true",
|
|
"feature.sdg": "true",
|
|
"instagram_handle": "CONSUL",
|
|
"mailer_from_address": "noreply@consul.dev",
|
|
"mailer_from_name": "CONSUL",
|
|
"meta_description": "Citizen participation tool for an open, "\
|
|
"transparent and democratic government",
|
|
"meta_keywords": "citizen participation, open government",
|
|
"meta_title": "CONSUL",
|
|
"org_name": "CONSUL",
|
|
"proposal_code_prefix": "MAD",
|
|
"proposal_notification_minimum_interval_in_days": 0,
|
|
"telegram_handle": "CONSUL",
|
|
"twitter_handle": "@consul_dev",
|
|
"twitter_hashtag": "#consul_dev",
|
|
"url": "http://localhost:3000",
|
|
"votes_for_proposal_success": "100",
|
|
"youtube_handle": "CONSUL"
|
|
}.each do |name, value|
|
|
Setting[name] = value
|
|
end
|
|
end
|