You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fluss.apache.org by "leekeiabstraction (via GitHub)" <gi...@apache.org> on 2026/02/20 20:15:56 UTC
[I] Setup Website for Client docs [fluss-rust]
leekeiabstraction opened a new issue, #356:
URL: https://github.com/apache/fluss-rust/issues/356
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/fluss-rust/issues) and found nothing similar.
### Description
Client documentation websites are mostly complete now. We need to setup the domain for the client doc website and also setup CI to publish to client doc website.
### Willingness to contribute
- [ ] I'm willing to submit a PR!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Setup Website for Client docs [fluss-rust]
Posted by "luoyuxia (via GitHub)" <gi...@apache.org>.
luoyuxia commented on issue #356:
URL: https://github.com/apache/fluss-rust/issues/356#issuecomment-3981656802
@leekeiabstraction Thanks for the investigation. I think publish from fluss-rust is better.
And I prefer to publish `fluss-rust` docs under `clients.fluss.apache.org/`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Setup Website for Client docs [fluss-rust]
Posted by "leekeiabstraction (via GitHub)" <gi...@apache.org>.
leekeiabstraction commented on issue #356:
URL: https://github.com/apache/fluss-rust/issues/356#issuecomment-3979434257
@luoyuxia @wuchong
For publishing the `fluss-rust` website, which approach should we take?
| | Publish from fluss-rust | Publish from fluss-website | Publish from new fluss-rust-website |
|--------------------------|-------------------------|-------------------------------|-------------------------------------|
| New repos needed | 0 | 0 | 1 |
| ASF tickets needed | 0 | 0 | 1 (new repo) |
| Cross-repo secrets | No | Yes (`GH_TOKEN`) | Yes (`GH_TOKEN`) |
| CI permission on source | `contents: write` | `contents: read` | `contents: read` |
| Coupling with fluss | None | High | None |
| Git bloat on source repo | Yes | No | No |
| Versioning complexity | Low (own branch) | High (preserve both) | Low (own branch) |
| Race conditions | None | Manage with concurrency group | None |
- Cross repo secrets: using `fluss-website` like approach requires configuring `fluss-rust` with secret to push to website repo
- CI permission on source: only read is needed when using `fluss-website` like approach because `fluss-rust` source branch does not need to be updated
- Coupling with fluss: sharing `fluss-website` couples `fluss` and `fluss-rust` websites. If either has bug, both stops deploying.
- Race conditions: publishing both `fluss` and `fluss-rust` around the same time may result in later workflow overwriting the result of earlier workflow. This can be worked around using git workflow concurrency group
Additionally, which of these do we prefer to publish `fluss-rust` docs under?
- `fluss.apache.org/fluss-rust/`
- `fluss.apache.org/clients/`
- `clients.fluss.apache.org/`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Setup Website for Client docs [fluss-rust]
Posted by "leekeiabstraction (via GitHub)" <gi...@apache.org>.
leekeiabstraction commented on issue #356:
URL: https://github.com/apache/fluss-rust/issues/356#issuecomment-3982975489
> I think publish from fluss-rust is better.
Okay, I can work the PR towards this. Note that this requires a branch containing doc build here, and when we do have further versions and want to keep versioned docs, the size of that branch will keep going. We can potentially think about migrating to website repo when that becomes an issue.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org