Conversation
Corrected relative paths to Studios documentation that were broken after the Studios docs reorganization. Updated links in configuration tables and Docker Compose template to point to the correct install-studios.md file. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Corrected relative paths in v25.1 and v25.2 that were pointing to incorrect locations after the Studios docs reorganization. Updated 7 broken links in configuration tables and 1 in Docker Compose template to point to the correct install-studios.md file. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
…with platform v26.1
bebosudo
requested review from
a team,
justinegeffen and
llewellyn-sl
as code owners
|
✅ Editorial Review Complete (PR type: content) - No issues found! Documentation looks good. Review by Claude Code editorial agents |
📝 Documentation Review Summary (PR type: content)
Review powered by Claude Code editorial agents To apply suggestions:
|
|
Thanks, @bebosudo! The changelog is done in a separate repo for review and then ported over when the release is ready. The branch for that will be created closer to the end of March. :) |
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
internal link checker is now passing |
| data-studio: | ||
| allowed-workspaces: [12345,67890] | ||
| ``` | ||
| 1. From Platform v26.1, Studios is enabled by default on all workspaces. To enable Studios on specific workspaces only, set the `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES` environment variable (e.g., `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES="12345,67890"`) on the Platform backend containers. To disable Studios for all workspaces, set `TOWER_DATA_STUDIO_ALLOWED_WORKSPACES=""` (an empty string). |
There was a problem hiding this comment.
Both of these approaches work, so I'm not necessarily complaining. But what's the point of moving away from tower.yml in favour of the environment variable way (particularly since previous docs referenced tower.yml)?
Is the intention to do this across all configurations? (i.e deprecate and eventually remove tower.yml as a configuration method)?
4 participants
Starting from Platform v26.1, Studios is enabled by default on all Workspaces, so there won't be any need to edit the tower.yml file anymore, since the WS's where it can be enabled can now be controlled by an env var. Shall we drop the tower.yml snippet altogether?
Also, I'm not sure where changelog updates for v26.1 should go. Is there a file? a PR? do we create it automatically? @justinegeffen