-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Theme not rendering, pathing issues #1421
Comments
What is your |
Hello bep, baseurl = "http://replace-this-with-your-hugo-site.com/" I'm currently connecting to the ec2 using the public ip, http://52.11.165.33/ should I change the baseurl to this ip? |
Hi @Fthree, Please read http://gohugo.io/overview/usage/ again and note the options, then try the following:
|
@anthonyfok I knew it was something simple that I was missing. The baseUrl got me, thank you very much. I'll give that page another thorough read. |
If I recall correctly, whenever the "hugo server" subcommand is used, the |
Thank you, I really appreciate your help. The whole thing is still a little bit foreign to me, glad you came through to my help! So the config.toml baseurl is overwritten for the command line --baseUrl? I attempted editing the config.toml baseUrl to the IP to no success. |
Yes, it is somewhat tricky. That's why we need to explicitly override If you are interested, please read #852 for a more thorough discussion. Perhaps eventually we will add a new option called |
@anthonyfok's point above was what I needed. It would be great if this were part of the tutorials. The Quickstart led me to use the Ananke Theme, which lead me to their example site to understand their config, which gave no indication that you have to change the baseUrl (since they are apparently using hugo server. In fact, this all could have been prevented for me if the gitlab tutorial had simply mentioned you would need to change your baseUrl. Right here would have been perfect: https://gohugo.io/hosting-and-deployment/hosting-on-gitlab/#wait-for-your-page-to-build Instead, I tried messing with git submodules on gitlab to make sure I had that right, or trying to put the akanke them inside my public folder, and a bunch of other things. :( |
Hi, I was able to set the baseURL properly. I am rendering hugo with github pages. |
@yashika51: the same happens to me (first time I use Hugo and first time I use Github Pages as well). I'm using the zzo theme. P.S. The preview with [Edit:] It works now. It seems that the theme files took more time to get uploaded to the Github server... I just waited and then everything worked as expected. |
I'm also using the same theme |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I've followed the https://gohugo.io/overview/quickstart/
I then followed the https://gohugo.io/overview/usage/ on deployment on a hugo-only server.
I run the server with:
sudo hugo server --bind=0.0.0.0 --port=80 --theme=hyde
I end up with a non-css/js site. This all works locally, however.
when I attempt to open the site in chrome I get " Failed to load resource: the server responded with a status of 404 (Not Found) " on "http://localhost/css/hyde.css, syntax.css and poole.css". I assume my Pathing is incorrect somewhere.
All files remained untouched, the config.toml included (meaning, it is the default version when creating a site using hugo new site command)
I'm working on an EC2 Ubuntu.
The text was updated successfully, but these errors were encountered: