mirror of
https://github.com/superseriousbusiness/gotosocial.git
synced 2025-10-31 02:32:25 -05:00
3ba49aed45
# Description > If this is a code change, please include a summary of what you've coded, and link to the issue(s) it closes/implements. > > If this is a documentation change, please briefly describe what you've changed and why. Profile fields, right? So I made them a configurable amount and show them on the instance features. Closes #1876 All changes I did are described in the commits. I tried to cover as much as possible, but I don't know this codebase to know what I've missed. I have tested it manually and it works (settings page, `/api/v1/instances`, server-side validation). Not done: - An "Add profile fields" button, so that instances with a high profile fields count (e.g. 100) aren't an issue when trying to skip the profile fields (in some form, accessibility) - Updating the swagger docs that specify a specific amount of profile fields for the updating endpoint (not sure how to proceed with that) - Unchecked checklist items ## Checklist Please put an x inside each checkbox to indicate that you've read and followed it: `[ ]` -> `[x]` If this is a documentation change, only the first checkbox must be filled (you can delete the others if you want). - [X] I/we have read the [GoToSocial contribution guidelines](https://codeberg.org/superseriousbusiness/gotosocial/src/branch/main/CONTRIBUTING.md). - [x] I/we have discussed the proposed changes already, either in an issue on the repository, or in the Matrix chat. - [X] I/we have not leveraged AI to create the proposed changes. - [x] I/we have performed a self-review of added code. - [X] I/we have written code that is legible and maintainable by others. - [ ] I/we have commented the added code, particularly in hard-to-understand areas. - [X] I/we have made any necessary changes to documentation. - [ ] I/we have added tests that cover new code. - [X] I/we have run tests and they pass locally with the changes. - [x] I/we have run `go fmt ./...` and `golangci-lint run`. Notes about checklist: - ["Approval" to work on this reference](https://matrix.to/#/!mlPctfMHjyopbOnliM:superseriousbusiness.org/$P0Z1Qmny6GNIgxhre69gll8KSD690HC8nVvNpXmu3nU?via=superseriousbusiness.org&via=matrix.org&via=tchncs.de) - `golangci-lint run` output ignored due to complaining about ffmpeg and some other code I didn't touch Reviewed-on: https://codeberg.org/superseriousbusiness/gotosocial/pulls/4175 Reviewed-by: kim <gruf@noreply.codeberg.org> Co-authored-by: Jackson <jackson@jacksonchen666.com> Co-committed-by: Jackson <jackson@jacksonchen666.com>
75 lines
2.6 KiB
Markdown
75 lines
2.6 KiB
Markdown
# Accounts
|
|
|
|
## Settings
|
|
|
|
```yaml
|
|
###########################
|
|
##### ACCOUNTS CONFIG #####
|
|
###########################
|
|
|
|
# Config pertaining to creation and maintenance of accounts on the server, as well as defaults for new accounts.
|
|
|
|
# Bool. Allow people to submit new sign-up / registration requests via the form at /signup.
|
|
#
|
|
# Options: [true, false]
|
|
# Default: false
|
|
accounts-registration-open: false
|
|
|
|
# Bool. Are sign up requests required to submit a reason for the request (eg., an explanation of why they want to join the instance)?
|
|
# Options: [true, false]
|
|
# Default: true
|
|
accounts-reason-required: true
|
|
|
|
# Int. Number of approved sign-ups allowed within
|
|
# 24hrs before new account registration is closed.
|
|
#
|
|
# Leaving this count at the default essentially limits
|
|
# your instance to growing by 10 accounts per day.
|
|
#
|
|
# Setting this number to 0 or less removes the limit.
|
|
#
|
|
# Default: 10
|
|
accounts-registration-daily-limit: 10
|
|
|
|
# Int. Number of new account sign-ups allowed in the pending
|
|
# approval queue before new account registration is closed.
|
|
#
|
|
# This can be used to essentially "throttle" the sign-up
|
|
# queue to prevent instance admins becoming overwhelmed.
|
|
#
|
|
# Setting this number to 0 or less removes the limit.
|
|
#
|
|
# Default: 20
|
|
accounts-registration-backlog-limit: 20
|
|
|
|
# Bool. Allow accounts on this instance to set custom CSS for their profile pages and statuses.
|
|
# Enabling this setting will allow accounts to upload custom CSS via the /user settings page,
|
|
# which will then be rendered on the web view of the account's profile and statuses.
|
|
#
|
|
# For instances with public sign ups, it is **HIGHLY RECOMMENDED** to leave this setting on 'false',
|
|
# since setting it to true allows malicious accounts to make their profile pages misleading, unusable
|
|
# or even dangerous to visitors. In other words, you should only enable this setting if you trust
|
|
# the users on your instance not to produce harmful CSS.
|
|
#
|
|
# Regardless of what this value is set to, any uploaded CSS will not be federated to other instances,
|
|
# it will only be shown on profiles and statuses on *this* instance.
|
|
#
|
|
# Options: [true, false]
|
|
# Default: false
|
|
accounts-allow-custom-css: false
|
|
|
|
# Int. If accounts-allow-custom-css is true, this is the permitted length in characters for
|
|
# CSS uploaded by accounts on this instance. No effect if accounts-allow-custom-css is false.
|
|
#
|
|
# Examples: [500, 5000, 9999]
|
|
# Default: 10000
|
|
accounts-custom-css-length: 10000
|
|
|
|
# Int. The maximum number of profile fields allowed for each account.
|
|
#
|
|
# Note that going way higher than the default might break federation.
|
|
#
|
|
# Examples: [4, 6, 12]
|
|
# Default: 6
|
|
accounts-max-profile-fields: 6
|
|
```
|