[DOCS-6418] Fix libgiza bug where repos are cloned into wrong directory Created: 20/Oct/15  Updated: 27/Jul/16  Resolved: 22/Oct/15

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Allison Reinheimer Moore Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 7 years, 29 weeks ago

 Description   

The first time you build a repo with giza/libgiza, sadness happens and the docs-tools and docs-assets (and probably some others?) repos are cloned into the root directory rather than build, and then there are errors, and it is sad.



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

Comment by Allison Reinheimer Moore [ 20/Oct/15 ]

Hi mike.laspina! Glad you found the workaround. Once you've got the repo set up, you shouldn't run into any trouble (we only found the issue when onboarding a new colleague). We'll still be fixing the bug to avoid the shenanigans in the first place

Comment by Mike LaSpina (Inactive) [ 20/Oct/15 ]

I got the html build to work via the following procedure:

1) Clone the repo https://github.com/mongodb/docs
2) Create the folder ~docs/build
3) Move the folder ~docs/docs-tools to ~docs/build/docs-tools
4) Copy the folder ~docs/source/.static to ~docs/.static (note, I did not try a move, but that may work here as well)
5) Run 'make html' from the ~docs folder, and it worked!

Generated at Thu Feb 08 07:52:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.