Skip to content
This repository has been archived by the owner on Mar 10, 2024. It is now read-only.

Deploy Errors #54

Closed
JimLynchCodes opened this issue Oct 9, 2018 · 6 comments
Closed

Deploy Errors #54

JimLynchCodes opened this issue Oct 9, 2018 · 6 comments

Comments

@JimLynchCodes
Copy link

I followed the Gatsby guide for deploying to gh-pages, but it did not work.

raw_plants_foundation_and_raw-plants-foundation-website____git-projects_raw-plants-foundation-website__-____content_meta_config_js__raw-plants-foundation-website__and_raw-plants-foundation-website -bash _111x28

I get many errors about files not being found even though they are there in the final directory named "public".

@JimLynchCodes
Copy link
Author

In my content/meta/config:

  siteUrl: "https://jimtheman.github.io",
  pathPrefix: "/Raw-Plants-Foundation-Website",

@JimLynchCodes
Copy link
Author

then:

gatsby build --prefix-paths && gh-pages -d public

@JimLynchCodes
Copy link
Author

Looks like it is not using the prex path even when I enter a prefixPath in the config.
raw_plants_foundation

@JimLynchCodes
Copy link
Author

please sir, is there anyone who can think of to be done?

@JimLynchCodes
Copy link
Author

nevermind,

The real issue was that "pathPrefix" needed to be at the top level of gatsby-config.js, not nested within siteMetadata. This is probably just an inconsistency with new versions of gatsby, and I should probably let the maintainer of gatsby starter hero blog know that his template is not correct syntax anymore...

@JimLynchCodes
Copy link
Author

oh, this is gatsby starter hero blog...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant