Hosting on GitHub Pages

[oliviertassinari]

• I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

I can host a Next.js app on a GitHub Pages.

Current Behavior

As far as I have digged into the issue, we can't host a Next.js app on a GitHub Pages because of the location of the hosting: http://username.github.io/project-name/. It would be working perfectly if we hadhttp://project-name.github.io/.

Steps to Reproduce (for bugs)

Humm. I'm not sure it's relevant. I can provide something if it help. I noticed the issue with http://oliviertassinari.github.io/react-swipeable-views/.

Context

Deploying a Next.js app into GitHub Pages guide is misleading. It's not possible as far as I know.

Your Environment

Tech	Version
next	4.1.4

[oliviertassinari]

I solved the issue with Firebase + Cloudfront : https://react-swipeable-views.com/. For smaller projects, I wish I could simply deploy to a GitHub Page.

[sergiodxa]

You can define an assetsPrefix on next.config.js to define /project-name as your asset prefix so everyfile will be loaded from that URL instead of /. Check /~https://github.com/zeit/next.js#cdn-support-with-asset-prefix.

That way you can deploy to a GH page, the Wiki guide explain how to avoid issues with jekyll ignoring files prefixed with _ like _next.

[oliviertassinari]

@sergiodxa You are right, assetsPrefix is missing from the guide.

However, it only solves the assets loading issue. You still gonna have issues with the navigation. <Link href="/about"> will lead you to http://username.github.io/about not http://username.github.io/project-name/about. So it's working client side, but render a 404 if you reload.

[thierryc]

Take a look to my config file.
/~https://github.com/anotherplanet-io/Next-React-Components/blob/master/next.config.js

[oliviertassinari]

@thierryc Thanks for providing a reproduction example 👍 .

1. Navigate to https://anotherplanet-io.github.io/Next-React-Components/
2. Click on the Components link
3. Refresh 💥

[thierryc]

This may can help you.
/~https://github.com/zeit/next.js/tree/master/examples/with-universal-configuration

[thierryc]

@oliviertassinari I fixe it. (hope)

try :

1. Navigate to https://anotherplanet-io.github.io/Next-React-Components/
2. Click on the Components link
3. Refresh 👍 or 👎

[oliviertassinari]

@thierryc The following approach is interesting:

const prod = process.env.NODE_ENV === 'production'

module.exports = {
  'process.env.BACKEND_URL': prod ? 'https://anotherplanet-io.github.io/Next-React-Components' : ''
}

Unfortunately, it comes with a new issue. Any page transition will reload the whole page. You lose the client page transitions. For instance, you can't preload the next page.

[thierryc]

Yes I know. Interesting approach but 👎 solution.
I am working on it. Any suggestion ?

[jabacchetta]

By the way, @thierryc — not sure if you're aware, but your out directory is missing the empty .nojekyll file, which is why all of your _next files are returning a 404.

I'm actually now using the same approach as @thierryc for the env variable, because the assetsPrefix only applies to the _next directory files, meaning the static directory files return a 404. Adding the env variable and prepending to asset links fixes this.

Any other recommendations? @sergiodxa @oliviertassinari

Here's my page, for reference.

[thierryc]

Thank you @jabacchetta, I add it!

But the real problem is:

The next router is /absolute

1st loading: the route is https://anotherplanet-io.github.io/Next-React-Components
When you use a link the route becomes:

• https://anotherplanet-io.github.io/ap-grid-layout/ (404)

not

• https://anotherplanet-io.github.io/Next-React-Components/ap-grid-layout/ (200)

If you reload the page, you get a 404 error.

I add the prefix ('process.env.BACKEND_URL' ) to every link.
The site works.
No more 404 error!

const prod = process.env.NODE_ENV === 'production'

module.exports = {   'process.env.BACKEND_URL': prod? 'https://anotherplanet-io.github.io/Next-React-Components' : '' }

BUT Unfortunately, it comes with a new issue. Thank you to @oliviertassinari to point it !
Any page transition will reload the whole page.
You lose the client page transitions.
For instance, you can't preload the next page.

I also try <base href='path' > . No success.

Do you have any suggestions.

[thierryc]

Eureka ! 🛁 @sergiodxa @oliviertassinari @jabacchetta

👍 use:

<Link href={ '/ap-grid-layout' } as={ process.env.BACKEND_URL + '/ap-grid-layout' }><a>Grid Layout</a></Link>

env-config.js

const prod = process.env.NODE_ENV === 'production'

module.exports = {   'process.env.BACKEND_URL': prod? '/Next-React-Components' : '' }

This solution works for me !
https://anotherplanet-io.github.io/Next-React-Components/

Do you confirm ? Refresh 👍 or 👎

[thierryc]

I create an example for Next.js

A Github gh-pages Example to replace Doctor Jekyll.

Test it :

/~https://github.com/thierryc/Next-gh-page-exemple/

https://thierryc.github.io/Next-gh-page-exemple/

/~https://github.com/thierryc/next.js

[jabacchetta]

Looking good, @thierryc! I've got this exact setup on my page as well. The deploy npm script will definitely come in handy.

[thierryc]

Yes git is handy (git subtree push) !

next build 
&& next export 
&& touch out/.nojekyll
&& git add out/ 
&& git commit -m \"Deploy Next.js to gh-pages\" 
&& git subtree push --prefix out origin gh-pages"

[oliviertassinari]

@thierryc Looks like it's working :).

[jabacchetta]

Also, for anyone that is using a custom domain:

• The env url and assetsPrefix are not necessary. You only need these when using GitHub's domain (which has a /project-name path appended to the url).

• You can add on to the deploy command to create the CNAME file for you. GitHub detects this file and automatically updates the custom domain setting. Replace example.com with your custom domain.

next build 
&& next export 
&& touch out/.nojekyll
&& touch out/CNAME
&& echo \"example.com\" >> out/CNAME
&& git add out/ 
&& git commit -m \"Deploy to gh-pages\" 
&& git subtree push --prefix out origin gh-pages"

[adibas03]

While using babel-transform method,there is a resulting cache issue.
Where the cache prevents update of correct data.
This can be solved using this little trick:
#1103 (comment)

[siakaramalegos]

I got most of my app to publish correctly in gh-pages (a project branch). My one problem is that the asset path I have for a background image is not getting properly prefixed in the build. I used styled-jsx to write the CSS - here is a snippet:

    <div className="root">
      <h1>{title}</h1>
      {text && <p>{text}</p>}
      <style jsx>{`
        .root {
          color: white;
          background: #ccc url(${imageSrc}) no-repeat center center;
          background-size: cover;
          padding: 100px;
        }
        h1 {
          font-size: 3em;
          font-weight: 100;
        }
      `}</style>
    </div>

Works fine in regular served mode and regular static mode (without project prefix). I have another project that works fine when I set publicPath in my webpack config with /{repo name}/, but I have separate CSS files for that. Any suggestions?

[shuding]

An easier approach is using push-dir to push a directory to a specific branch.
So you don't need to track the out dir or manually commit in git.

First install via NPM npm i -g push-dir then you can use:

next build 
&& next export 
&& touch out/.nojekyll
&& touch out/CNAME
&& echo \"example.com\" >> out/CNAME
&& push-dir --dir=out --branch=gh-pages

(based on @jabacchetta's script)

[Janpot]

@thierryc I guess you could also wrap Link to add the prefix automatically:
(Using the old context API, the new one doesn't seem to work for me in next.js)

import Link from 'next/link';
import React from 'react';
import PropTypes from 'prop-types';

export default class PrefixedLink extends React.Component {
  render () {
    const { href, as = href, ...props } = this.props;
    const { prefix = '' } = this.context;
    return <Link href={href} as={`${prefix}${as}`} {...props} />;
  }
}

PrefixedLink.contextTypes = {
  prefix: PropTypes.string
};

export class PathPrefix extends React.Component {
  getChildContext () {
    return { prefix: this.props.prefix || '' };
  }

  render () {
    return this.props.children;
  }
}

PathPrefix.childContextTypes = {
  prefix: PropTypes.string
};

Would be used as

import Link, { PathPrefix } from './my-link'

export function MyApp () {
  return (
    <PathPrefix prefix={process.env.BACKEND_URL}>
      <Link href='/about'>About</Link>
    </PathPrefix>
  )
}

Maybe this could even be part of the router API? like

import { withPathPrefix } from `next/router`

[timneutkens]

This issue can be closed as deploying to github pages works fine, eg zeit-status.co.

[hipstersmoothie]

I've pubished an article that includes steps on how to push to github pages. This might also be helpful for some.

[realtebo]

@hipstersmoothie thanks a lot for your article. I'll try. Could you post the similar but not identical procedure to publish to a personal page?

[hipstersmoothie]

That was the procedure on how to publish to a personal github.io page. So i'm not sure what you're asking.

[tbntdima]

Hi guys, here is my solution for altering the links (if you deploy on not main repository), hope it will be helpful to somebody:

Next allows to set environmental variables in next.config.js now. This way all the configurations are stored in the same place.
So here I declare a linkPrefix variable to use later.

next.config.js

const isProduction = process.env.NODE_ENV === 'production';

module.exports = {
  assetPrefix: isProduction ? '/next-hello-world' : '',
  publicRuntimeConfig: {
    // used in '/components/Link.js/', for more details go to the component itself
    linkPrefix: isProduction ? '/next-hello-world' : ''
  }
};

Here I create a custom HOC, which basically adds the linkPrefix from before to all the links 'as'.
This way page will be ok on reload.

components/Link.js

/**
 * Higher order component, which is based on 'next/link'
 * When app is deployed on github pages repository which is not the main one
 * e.g https://username.github.io/repository/
 * standard 'next/link' is not wokring properly, it doesn't add the 'reporsitory'
 * to url so instead of expected 'https://username.github.io/repository/about',
 * it would be 'https://username.github.io/about/
 * This HOC solves the problem, by adding the prefix (which is defined in next.config.js)
 * to 'as' property
 */
import getConfig from 'next-server/config';
import Link from 'next/link';

const { publicRuntimeConfig } = getConfig();
const linkPrefix = publicRuntimeConfig.linkPrefix;

const PrefixedLink = ({ href, as = href, children }) => (
  <Link href={href} as={`${linkPrefix}${as}`}>
    {children}
  </Link>
);

export default PrefixedLink;

here is my package.json scripts, you will need to install gh-pages though.

    "export": "yarn run build && next export",
    "deploy": "yarn export && touch out/.nojekyll && gh-pages -t -d out"

demo:
https://dmitriyaa.github.io/next-hello-world/

[melanievillela]

I've pubished an article that includes steps on how to push to github pages. This might also be helpful for some.

The link to your article isn't working. Could you update it? I'm having a difficult time deploying my build.

[thierryc]

@melanievillela, I don't know where is this article but, how may I can help you?
What is your issues ?

This is my first example /~https://github.com/thierryc/Next-gh-page-example.
I can update it. What is you next version ?

[melanievillela]

@thierryc, I am using 6.4.1

[thierryc]

@melanievillela I will update my example. I keep you posted.

[thierryc]

@melanievillela

/~https://github.com/thierryc/Next-gh-page-example is up to date now.

I use gh-pages package to publish it. (More simple).
I test it on Next.js v9.1.4.

[melanievillela]

@thierryc, why does https://thierryc.github.io/ show 404? I am trying to deploy to https://melanievillela.github.io/ and I used build and export but still is not working.

[thierryc]

@melanievillela the example is a hp-page project, not a user gh-page.

The path is not the same.

I will do my personal gh-page today (or tomorrow). I keep you posed (I will share it to you)

[thierryc]

@melanievillela My personal gh-page example /~https://github.com/thierryc/thierryc.github.io

2 interesting point.

• my default branch is the source (not master)
• Master is the website, source is the src of the web site.

I use deploy to push the source into the master.

If you get an issue to push it (deploy) just delete the master and deploy again.

npm run deploy

[melanievillela]

@thierryc - I will look at it very interesting about the default branch!

[thierryc]

@melanievillela The only way to keep your repo clean...

[rafaeleyng]

There are a lot of mentions to assetsPrefix. The property is actually called assetPrefix.

[xixixao]

See full working instructions here: #9753 (comment) (hopefully it'll get folded onto the wiki page).

[thierryc]

@rafaeleyng "assetPrefix" nice catch.

[kas]

Adding a .nojekyll file in the same directory that contains the _next folder fixed the issue for me. There are more details in this Stack Overflow question.

[pojntfx]

@kas's solution fixed it for me, even when using a custom domain. See: pojntfx/nebulark@911ca45

[samuel-ping]

@kas's solution worked for me as well, except I also had to add the following to my next.config.js:

module.exports = {
    basePath: '/<repo_name>',
    assetPrefix: '/<repo_name>',
    ...
}

Which I got from here.

This is because, from what I saw in my Chrome devtools, without the basePath and/or assetPrefix, my browser wasn't fetching assets from me.github.io/myrepo/_next/<path-to-file>, but rather me.github.io/_next/<path-to-file>.

My site is deployed from a gh-pages branch (not default branch) with no custom domain name.

[Yrobot]

Also, for anyone that is using a custom domain:

• The env url and assetsPrefix are not necessary. You only need these when using GitHub's domain (which has a /project-name path appended to the url).
• You can add on to the deploy command to create the CNAME file for you. GitHub detects this file and automatically updates the custom domain setting. Replace example.com with your custom domain.

next build 
&& next export 
&& touch out/.nojekyll
&& touch out/CNAME
&& echo \"example.com\" >> out/CNAME
&& git add out/ 
&& git commit -m \"Deploy to gh-pages\" 
&& git subtree push --prefix out origin gh-pages"

actually, when i use custom domain setting. the files in the _next dir can't be fetched.
here is my repo
assets file can be fetched, like http://blog.yrobot.top/assets/person.svg .
the files in the _next dir can't be fetched. like http://blog.yrobot.top/_next/static/css/38f07f2a72553a556357.css

[SquireOfSoftware]

Damn, I did not realise that this was so frustratingly complex, so there appears to be a mix of adding assetPrefix and basePath mixed in with .nojekyll fixes here and there...I guess I will have to try them all...

EDIT:

So I had to do a few things, to get this to nicely work, the back end is an absolute mess.

The site is hosted on the username.github.io domain which means that you have repository by the same name. So the hosting comes out to be https://username.github.io/username.github.io/_next/whatever.

Currently spent way too long on this damned process to get this to work, but basically I had a .nojekyll blank file on the root of the directory (my nextJS project lives one level down in the main repo).

Then I had this in my next.config.js file:

module.exports = {
  ...
  assetPrefix: '/',
  basePath: '/username.github.io'
}

I have a bash script that just does a:

next build && next export
cp -r out/ ../

Where I do the build inside the directory (on the branch that I want to deploy the ghpages) and the copy out the output to the root of the directory, commit the build and then push the changes out to github.

Then switch the branch of ghpages to the branch...I hate at how I have to do this must stuff just to host the darn HTML page.

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.