Added post and updates for v0.25.1
This commit is contained in:
parent becc495dd2
commit 91002f38e5
6 changed files with 91 additions and 7 deletions
| @ -52,3 +52,19 @@ in your `.env` file: | |||
```bash | ||||
APP_AUTO_LANG_PUBLIC=false | ||||
``` | ||||
| ||||
### Localised Date Formatting | ||||
| ||||
BookStack does support the localisation of date formats but it does depend on the intended locales being installed | ||||
on the host system. If using ubuntu, you can manage installed locales via the command: | ||||
| ||||
```bash | ||||
sudo dpkg-reconfigure locales | ||||
``` | ||||
| ||||
For other operating systems this may be different. After installing new locales you may need to restart any running PHP processes. | ||||
For example, On Ubuntu, running PHP7.2: | ||||
| ||||
```bash | ||||
sudo systemctl restart php7.2-fpm.service | ||||
``` |
| @ -53,14 +53,12 @@ TWITCH_AUTO_CONFIRM_EMAIL=true | |||
| ||||
1. Open the [Google Developers Console](https://console.developers.google.com/). | ||||
2. Create a new project (May have to wait a short while for it to be created). | ||||
3. Select 'Enable and manage APIs'. | ||||
4. Enable the 'Google+ API'. | ||||
5. In 'Credentials' choose the 'OAuth consent screen' tab and enter a product name ('BookStack' or your custom set name). | ||||
6. Back in the 'Credentials' tab click 'New credentials' > 'OAuth client ID'. | ||||
7. Choose an application type of 'Web application' and enter the following urls under 'Authorized redirect URIs', changing `https://example.com` to your own domain where BookStack is hosted: | ||||
3. In 'Credentials' choose the 'OAuth consent screen' tab and enter a product name ('BookStack' or your custom set name). | ||||
4. Back in the 'Credentials' tab click 'New credentials' > 'OAuth client ID'. | ||||
5. Choose an application type of 'Web application' and enter the following urls under 'Authorized redirect URIs', changing `https://example.com` to your own domain where BookStack is hosted: | ||||
- `https://example.com/login/service/google/callback` | ||||
- `https://example.com/register/service/google/callback` | ||||
8. Add or set the following items in your `.env` file like so: | ||||
6. Add or set the following items in your `.env` file like so: | ||||
```bash | ||||
# Replace the below (including '{}' braces) with your Google API_KEY and API_SECRET | ||||
GOOGLE_APP_ID={google_app_id} | ||||
| @ -69,7 +67,7 @@ TWITCH_AUTO_CONFIRM_EMAIL=true | |||
# APP_URL Needs to be set to your BookStack base url | ||||
APP_URL=http://mybookstackurl.com | ||||
``` | ||||
10. All done! Users should now be able to link their social accounts in their account profile pages and also register/login using their Google accounts. | ||||
7. All done! Users should now be able to link their social accounts in their account profile pages and also register/login using their Google accounts. | ||||
| ||||
--- | ||||
| ||||
| |
| @ -75,6 +75,27 @@ By default BookStack will generate a valid Amazon S3 URL for uploaded images. If | |||
STORAGE_URL=https://images.example.com | ||||
``` | ||||
| ||||
#### Non-Amazon, S3 Compatible Services | ||||
| ||||
Via the s3 connection BookStack does support s3-compatible services such as [Minio](https://www.minio.io/). Read the above S3 details to get an idea of general setup. | ||||
For non-Amazon services the configuration, to be placed in the `.env` file, is a little different: | ||||
| ||||
```bash | ||||
STORAGE_TYPE=s3 | ||||
STORAGE_S3_KEY=your-service-key | ||||
STORAGE_S3_SECRET=your-service-secret-key | ||||
STORAGE_S3_BUCKET=your-service-bucket-name | ||||
| ||||
STORAGE_S3_ENDPOINT=https://your-service-base-endpoint.com:8080 | ||||
STORAGE_URL=https://your-service-base-endpoint.com:8080/your-service-bucket-name | ||||
``` | ||||
| ||||
Take note of how the first part of the `STORAGE_URL` path is the bucket name. This is important to ensure image URLs are set correctly. | ||||
| ||||
BookStack's functionality to set image URL's as publicly accessible will likely not work for third-party services so you'll need to ensure files under the `<your_bucket>/uploads/images` path have policy or permissions to be publicly accessible. If using Minio you can add the following to the bucket policy: | ||||
| ||||
 | ||||
| ||||
--- | ||||
| ||||
### Changing Upload Limits | ||||
| |
Loading…
Add table
Add a link
Reference in a new issue