glitch-soc/config/settings.yml
Claire a6147a831f Merge commit '02ea16150647ac3baf0bb8a89203ccc7200b4a2f' into glitch-soc/merge-upstream
Conflicts:
- `app/lib/themes.rb`
- `app/views/layouts/application.html.haml`
- `app/views/layouts/embedded.html.haml`
- `app/views/layouts/error.html.haml`
- `config/settings.yml`

All these conflicts are because glitch-soc and upstream have different theming
systems and upstream changed a few things to have dynamic theme selection based
on system settings.

Conflicts were solved to take that into account, and `current_theme` has been
changed in the process to return a tuple of `[flavour, skin]` to be used in
the `theme_style_tags` helper.
2024-05-01 14:25:47 +02:00

57 lines
1.4 KiB
YAML

# This file contains default values, and does not need to be edited. All
# important settings can be changed from the admin interface.
defaults: &defaults
site_title: 'Mastodon Glitch Edition'
site_short_description: ''
site_description: ''
site_extended_description: ''
site_terms: ''
site_contact_username: ''
site_contact_email: ''
registrations_mode: 'none'
profile_directory: true
closed_registrations_message: ''
timeline_preview: false
show_staff_badge: true
preview_sensitive_media: false
noindex: false
flavour: 'glitch'
skin: 'system'
trends: true
trends_as_landing_page: true
trendable_by_default: false
trending_status_cw: true
hide_followers_count: false
reserved_usernames:
- admin
- support
- help
- root
- webmaster
- administrator
- mod
- moderator
disallowed_hashtags: # space separated string or list of hashtags without the hash
bootstrap_timeline_accounts: ''
activity_api_enabled: true
peers_api_enabled: true
show_reblogs_in_public_timelines: false
show_replies_in_public_timelines: false
default_content_type: 'text/plain'
show_domain_blocks: 'disabled'
show_domain_blocks_rationale: 'disabled'
outgoing_spoilers: ''
require_invite_text: false
backups_retention_period: 7
captcha_enabled: false
development:
<<: *defaults
test:
<<: *defaults
production:
<<: *defaults