Fixes: #82
Updates the getTokens.sh script to use the correct name "workspace admin token" when fetching the admin token from the Tinybird API.
The script was previously using "admin token" which does not correspond to any token returned by the API, causing it to fail when extracting the admin token from the API response. This change ensures the correct token is identified and output for the user.
It seems mail.from is required in the latest version (Ghost 6.0), otherwise mail setting won't work, which would result in the following log: "Missing mail.from config, falling back to a generated email address. Please update your config file and set a valid from address"
no ref
Refactored the activitypub env vars:
- Removed `USE_MQ` as this is only required when the value needs to be set to `true`
- Removed `PORT` as the application is now running on port 8080 by default
- Removed `ALLOW_PRIVATE_ADDRES` as this is not needed for `production` environment
- Added `ACTIVITYPUB_COLLECTION_PAGE_SIZE` as this is required for the
`following` dispatcher to work correctly
- Added link to documented env vars
no ref
- The only real desire here is to make the renovate PRs a bit easier and nicer to reach
- If we don't specify the exact version it creates PRs that are a bit confusing and aren't clear that its bumping a minor version
- The main meaningful change here is commenting the GHOST_VERSION variable
- I've also reordered the blocks to prioritise things in the documented setup flow
- Made various changes to the comments for clarity
ref: https://github.com/TryGhost/ghost-docker/pull/40
- Docker published RC2 on Friday I think
- Note 1: I just cut RC3, but that won't be available yet!
- Note 2: we prob need to rethink how we do versioning so we aren't pinning to exact versions
This will only have an effect when the version isn't set in the .env file and we have it in the .env.example but did still need updating as the fallback.
- Added a section title to each block that can be uncommented, so that we can reference this in the documentation
- Removed the first comment line as that seems out of date and confusing
- Minor improvements to some language and spelling for clarity
no ref
- In this redirect instance we're redirecting from `example.com` -> `www.example.com` so can actually use `{$DOMAIN}` here
- We can't in the first line of this block because Caddy doesn't (as far as I can currently tell) let us do a regex on it before putting it in to config
no ref
- Our ActivityPub framework lets users set their AP username to index@example.com and have Ghost on www.example.com (ie instead of having their AP user be index@www.example.com)
- To do this users _must_ redirect from the non-www domain -> the www domain as the AP protocol will do lookups on the non-www path to validate and communicate to that username on the web
- Without this AP will fail since domains can't communicate with AP as there wont be redirects for them to follow
- Our setup docs recommend having Ghost Admin on a separate domain from the content domain
- This lets users optionally set this up if they want whilst continuing to align Admin <-> content domain through templates
- We want customers to now copy the example Caddyfile so this still gives people the option but also makes it easier for customers who don't want to redirect themselves
