The purpose of this repository is to host the board's JSON file exported (using brd2json from my Fusion360 Electronics).
Every time a commit is made to this repository a Github Actions CI+CD pipeline (which uses iBOM and github-pages to generate an html page of the interactive BOM and deploy it to the github pages.
So ultimately I can see the iBOM from another computer/mobile device/tablet near my soldering station during assembly.
Mine's at: dattasaurabh82.github.io/InteractiveBOMs/
And I have a dedicated old phone for it near my soldering station, where if anything changes, I can refresh and get the new design.
TODO: Update image of setup
In your GitHub repository settings
, you need to configure GitHub Pages:
- Go to your repository's
Settings
- In the left sidebar, click
Pages
- Under
Build and deployment
:- For
Source
, selectGitHub Actions
-
Do not select
Deploy from a branch
since we're using the Actions workflow
- For
That's it! You don't need to configure anything else in the Pages settings.
The workflow we set up will handle everything:
- Building the site (generating the iBOM HTML)
- Creating the necessary artifacts
- Deploying to GitHub Pages
The first time you run the workflow, GitHub Pages will be automatically set up.
The URL where your site will be published will be shown in:
- The workflow run output
- Your repository's Pages settings
- Usually in the format:
https://<username>.github.io/<repository>/
-
Go to the archived repo of brd2json and switch to eagle-branch
-
In Fusion 360 electronics, when you are in the PCB Layout, from the
Automation
tab, select theULP
-
When the pop-up window appears, select
Browse
abd select thebrd2json.ulp
(from where you have cloned the brd2json in your local system) -
It will run and give you the path of the exported
.brd
and the.json
files -
Go there and copy them to this repo's root directory.
The Board's name and the JSON file's prefix name, doesn't matter. But make sure that at any given time there's only one .brd and it's respective .json file in the root directory of the repo.
-
Commit and Push and let the automation do it's magic.
My local repo of this, uses gitomatic to watch the folder and everytime I replace the .brd and .json files in there, it commits them to this remote repo and the generation of iBOM, followed by hosting of the html page, begins.