Mdbook for Internal wiki #174

Closed
opened 2024-06-04 05:32:22 +00:00 by Amanda · 12 comments
Member

We need to build the mdbook for the internal wiki. The reviewed draft is here..

As advised by Sabrina adding an issue on info_threefold_internal to be created there.

@gosam can I go ahead and assign this to Sasha?

We need to build the mdbook for the internal wiki. The reviewed draft is [here.](https://docs.google.com/document/d/1t50zSBwhS0EU12LZwj-BVcNGhghaAwwca2yYuJsTkgE/edit). As advised by Sabrina adding an [issue on info_threefold_internal](https://github.com/threefoldfoundation/info_threefold_internal/issues/20) to be created there. @gosam can I go ahead and assign this to Sasha?
Amanda was assigned by gosam 2024-07-03 08:06:36 +00:00
gosam added this to the June 10 – June 23 project 2024-07-03 08:06:40 +00:00
gosam modified the project from June 10 – June 23 to June 24 – July 07 2024-07-03 08:06:47 +00:00
Owner

Sasha started to build this and taught Amanda.

Amanda will work on this today in terms of filling out content.

We should be able to push this live tomorrow or the next day.

Sasha started to build this and taught Amanda. Amanda will work on this today in terms of filling out content. We should be able to push this live tomorrow or the next day.
Owner

The content has been updated but we need Kristof in order to push to the development branch, after which it needs to also go to production. We will reach out to Kristof today.

The content has been updated but we need Kristof in order to push to the development branch, after which it needs to also go to production. We will reach out to Kristof today.
Owner

@gosam
Thanks for the follow-up here.

We don't need Kristof to push to development. Main + dev branches are just protected, PRs are needed to push to those branches.

I discussed with Amanda and the flow is doing great for internal mdbook wiki. Also Timur is finalizing the CI/CD work so we will be able to set a flow to publish the websites online as we make updates!

I rebuilt the basic astro website, now the website works good. We just need to add content, which Amanda is doing, e.g. this PR.

How we work with gitea

  • Protect main + development branch
  • To change main or development
    • Create a branch: development_branch_name
    • Make PR from your branch to development
    • Owners of each repo can at their pace merge dev to main

Notes

Ideally we write this clearly in all repos we use. E.g. here

@gosam Thanks for the follow-up here. We don't need Kristof to push to development. Main + dev branches are just protected, PRs are needed to push to those branches. I discussed with Amanda and the flow is doing great for internal mdbook wiki. Also Timur is finalizing the CI/CD work so we will be able to set a flow to publish the websites online as we make updates! I rebuilt the basic astro website, now the website works good. We just need to add content, which Amanda is doing, e.g. [this PR](https://git.ourworld.tf/tfcoop/info_tf_internal/pulls/4). # How we work with gitea - Protect main + development branch - To change main or development - Create a branch: development_branch_name - Make PR from your branch to development - Owners of each repo can at their pace merge dev to main # Notes Ideally we write this clearly in all repos we use. [E.g. here](https://git.ourworld.tf/tfgrid/info_tfgrid#overview-1)
gosam modified the project from June 24 – July 07 to July 08 – July 21 2024-07-08 10:02:25 +00:00
Owner

@mik-tf When you are online can you please help clarify what needs to happen now in order to bring this live?

@mik-tf When you are online can you please help clarify what needs to happen now in order to bring this live?
Owner

Of course.

So Timur ia working on CI/CD workflow.

It is not production ready yet but almost.

So I can check in the following days to integrate this website into the workflow so it gets published when we push on dev or main branch

Of course. So Timur ia working on CI/CD workflow. It is not production ready yet but almost. So I can check in the following days to integrate this website into the workflow so it gets published when we push on dev or main branch
Owner

OK, but there is no way to bring it live now?

Thanks @mik-tf

OK, but there is no way to bring it live now? Thanks @mik-tf
Owner

There is a way. God's river.

So yeah I just made a PR to get a workflow done. Timur will be able to check soon I think.

projectmycelium/itenv#5

There is a way. God's river. So yeah I just made a PR to get a workflow done. Timur will be able to check soon I think. https://git.ourworld.tf/projectmycelium/itenv/pulls/5
Author
Member

Updated the June meeting notes, and created a PR which has been merged into the development branch. I discussed this with Mik and hoping to bring it live soon.

Updated the June meeting notes, and created a PR which has been merged into the development branch. I discussed this with Mik and hoping to bring it live soon.
gosam modified the project from July 08 – July 21 to July 22 – Aug 04 2024-07-23 12:22:19 +00:00
Owner

Waiting on @timur who is quite busy with other responsibilities

Waiting on @timur who is quite busy with other responsibilities
gosam modified the project from July 22 – Aug 04 to Aug 05 – Aug 18 2024-08-05 07:17:45 +00:00
Owner

Still waiting for Timur on this.

Still waiting for Timur on this.
Owner

The mdbook has been published!

https://internal.ourlibrary.tf
username: tfinternal
password: planetfirst

Now need to verify, share, and set a plan for ongoing updates.

The mdbook has been published! https://internal.ourlibrary.tf username: tfinternal password: planetfirst Now need to verify, share, and set a plan for ongoing updates.
gosam closed this issue 2024-08-21 09:38:56 +00:00
Owner

Has been shared, we will check monthly on it.

Has been shared, we will check monthly on it.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: tfgrid/circle_promotion#174
No description provided.