-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
bfdabe0
commit 03d2996
Showing
3 changed files
with
40 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# Outline configuration | ||
|
||
The `docker.env` file contains many configurations, but some configurations must | ||
be done through the website itself - the settings page. These settings are | ||
stored in the database, and thus not expressed through the `docker.env` file. | ||
|
||
When creating a new database, the following settings must be set through the | ||
website: | ||
|
||
- Arbitrary members should be viewers, and admins (board members and such) should | ||
be editors. Whilst it does not fully match this logic, the default role for | ||
new members must be set to `viewer` and not `editor`. | ||
- Logging in should only be done through our OAuth provider. Thus, logging in | ||
through email should be disabled. | ||
|
||
## Creating a new database and/or migrating | ||
|
||
Outline databases are maintained (and created?) using migrations. When updating | ||
the outline version, one _must_ create a backup beforehand, for the | ||
documentation states that the database will automatically be migrated once the | ||
service starts. | ||
|
||
When no database exists yet, this can be created by migrating/seeding. | ||
|
||
For both scenarios, I would like to refer you to [the official documentation](https://docs.getoutline.com/s/hosting/doc/docker-7pfeLP5a8t). | ||
|
||
## Updating to a newer version | ||
|
||
When updating outline to the latest version, please make a backup beforehand! | ||
As explained in the section above, the next time outline starts, a database | ||
migration will automatically occur. |