Skip to content

BeigeBadger/BeigeBadger.github.io

Repository files navigation

BeigeBadger.github.io

Created following a combination of these guides:

Development

Dependencies

  • NPM
  • Node
    • Will need Node v16 or lower as we're using a version of react-scripts that is less than v5 which has an OpenSSL issue. More information is available here.
    • nvs use node/16.20.2/x64

Commands

  • Should be run from inside the my-cv folder.

Deployment

Run npm run deploy to deploy (which will push to the cv branch that is configured here as the default branch for GitHub Pages).

NOTE: The deployment will only run if there are actually changes to the files that are served as part of the site. Hence running the deploy command multiple times or when only the README has been updated will generate a "Published" message but a deployment will not be created.

See here for deployment tips:

when get error branch already exists

{ ProcessError: fatal: A branch named 'gh-pages' already exists.

    at ChildProcess.<anonymous> (~/node_modules/gh-pages/lib/git.js:42:16)
    at ChildProcess.emit (events.js:180:13)
    at maybeClose (internal/child_process.js:936:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
  code: 128,
  message: 'fatal: A branch named \'gh-pages\' already exists.\n',
  name: 'ProcessError' }

The gh-pages module writes temporary files to a node_modules/.cache/gh-pages directory. The location of this directory can be customized by setting the CACHE_DIR environment variable.

If gh-pages fails, you may find that you need to manually clean up the cache directory. To remove the cache directory, run node_modules/gh-pages/bin/gh-pages-clean or remove node_modules/.cache/gh-pages.

Ideas

Printing

Chrome 0.6, 0.6 0.0, 0.0 Scale 80% Background graphics

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published