Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stable and dev channels #101

Open
XVilka opened this issue Aug 30, 2023 · 4 comments
Open

stable and dev channels #101

XVilka opened this issue Aug 30, 2023 · 4 comments

Comments

@XVilka
Copy link
Member

XVilka commented Aug 30, 2023

Currently, we have only one channel - master, which is deployed to https://book.rizin.re. I suggest:

  • Use the same branching scheme as other Rizin projects - stable and dev
  • Deploy stable on https://book.rizin.re/
  • Deploy dev on https://book-dev.rizin.re/ or a similar domain
  • See .github/workflow/mdbook.yml for branch settings (also update the base)
  • Update Rizin release checklist issue template to include the step of tagging the book too (optional?)
  • Point Rizin site to two version of the books - stable and dev
@wargio
Copy link
Member

wargio commented Aug 30, 2023

probably we should drop this, and embed the book into the main repo and then autogen the online website at each release (i.e. tag)

@ret2libc
Copy link
Member

@wargio book embedded into main code? I don't like it too much, there's plenty of stuff here.

@wargio
Copy link
Member

wargio commented Aug 30, 2023

no, i mean embedded in the rizin repo.
We can have images, etc.. here. just text in the main repo.

@XVilka
Copy link
Member Author

XVilka commented Aug 30, 2023

I agree with @ret2libc - it's better to keep it separate.

@XVilka XVilka pinned this issue Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants