This is my note fixed some problem you may encounter: 1.edit the hugo.toml with editors you have, personally I use notepad; 2. when write the hugo.toml-theme, mind the case, and also the name should be the directory name of that theme's;
This was a terrific video. I understand enough about the Hugo Way (and git) now to follow everything, even though it went quickly. I hope you will do more Hugo stuff because it is awesome.
Nice. That is actually a great way to get around the limitation of Github pages requiring a public repo. I can keep my drafts etc private now. Another option is syncing the public dir with something like copybara.
I got an error message when I first attempted the `git submodule` step at 07:59. The issue was that Hugo had already created a `public` directory for me. I deleted `public` before running the `git submodule` code and everything worked perfectly. Also, Github didn't publish my site instantly like it did for Ryan. I had to wait about 2 minutes before it loaded. But it did load and it looks fantastic. Hope this helps someone. Great video Ryan!
@@adityaranjan3000 Deleting public dir is OK. Look at 8:24, there is nothing except README in the public. Then run '$ hugo server' will re-create all the contents without removing 'README'
@@adityaranjan3000 Because the public folder is generated every time hugo builds a site, you need to delete it before executing the `git submodule` command.
It took me one and a half days. I almost gave up, and it always led to unexpected errors, but I am satisfied with the result! Thank you for the amazing instructions!
Thanks! I have just followed the process and my blog is live :D It took a bit longer than 10 minutes (Updating homebrew, automating the github pages update with github actions), but a fun journey! Keep up the good content.
I tried with the paper theme, but when I deploy the public files github only renders a plain HTML of my project. Any idea what I could have done wrong? EDIT: figured it out Messing with the URLs is confusing, you gotta make sure the URL in the config file matches the URL in the generated github page, and any build happens after the changes are saved. Using two repos with similar names, and following a terminal that has a similar name to one of the repos is also confusing. Also, Git is confusing. All that being said, thank you for your tutorial, it was the only one that got it working for me, even if it took me a couple of hours to make it happen. I am not a very educated person, so I still struggle a lot with these things. However, I would love if in future videos you could find a way to make things more easy to differentiate and avoid confusions for others like me. If not, that is okay too, it is your way of sharing things afterall. Thank you and have a good day.
Your tutorial is AWESOME! & directly to the point. I followed all the steps except creating two repositories, one where the actual content lives, and one for deployment. I didn't get it why we need 2 different repositories? Speaking of myself, I've created a single repository for the whole process, I found that this is more organized & less error-prone than 2 repositories approach for me.
Just ran into your channel by typing in hugo tutorial. Not sure if your channel is geared towards beginners or people with coding experience. Great tutorial, love the straightforward, no nonsense approach. My one criticism is it was hard to follow which folder you were typing your commands in with all the cd commands. I think it would be beneficial for you to slow down and reiterate which folder you're in first. I was lost for a bit because I tried to push origin in my public folder but it said it was not a git repo.
I had a tough time following this vid exactly the way it is. Maybe since I'm using Windows 11... idk. One workaround at 3:17 is inserting 'nano config.toml' and replacing the lines that need to be edited.
This is cool information in the video. But, instead of generating two folders and using git submodule to manage the files, using a github action to generate the static files could be more ergonomic.
thanks for the tutorial, Ryan! just wondering if there are benefits to not also pushing the contents from 'thesimplengineerblog' up to blog repo, to serve as a source control for the raw source code change instead of just having the public repo changelog?
Does the working code repo have to be public? I know the production repo obviously needs to be but can I do this where my "blog" repo is private? I guess I could try and see what happens! :)
i have a question though: how do i push future posts onto the repository from terminal? like do i just add the .md file directly into the public folder? then what?
@@coyotewld all this needs to ne done in the repo were we are storing the code right ? I did the same..... made some changes in my config.toml file and push it to the public repo but there was no change in my production repo (static file that we get) As this production repo is added as submodule in our public repo so do we need to do something with submodules also to reflect the changes in the production repo ??
We should not add to the public folder directly. We need to move up one folder above the public and add any new posts in to post/yourpost.md then hugo -t again, it will generate the static content corresponding to your new post in to public folder. then you cd to your public folder then push it. It will be reflected on the production site.
did u forgot to put/commit the blog repository on github? It will be possible to just put a new .md file inside the content folder without having to use hugo again?
extremely helpful video, though i did have to pause several times and iron out some kinks in my own code (i'm rusty...). thanks a lot for this video, ryan!
hi Ryan, just letting you know that the link to your notes (link you mention in the video, and that you left in your description box) is dead. If you could revive it that would be great, in any cases thank you for this very well done video. cheers
Followed every step, once hosted the site looks completely different. The only difference was I already had a public folder that I deleted and replaced with your method. Also clicking any links gives me a 404... Any suggestions?
I have the same issue. The site renders perfectly locally but when I upload to github it looks like the theme isnt applied and links give me 404 error - did you manage to fix this ?
![Jack Harlow - Hello Miss Johnson [Official Music Video]](http://i.ytimg.com/vi/Q86_nlRoIGw/mqdefault.jpg)
This is my note fixed some problem you may encounter:
1.edit the hugo.toml with editors you have, personally I use notepad;
2. when write the hugo.toml-theme, mind the case, and also the name should be the directory name of that theme's;
This tutorial is very well done. Everything that Ryan says is straight to the point. It's about the needed information - no show-off
i agree with @ukkir7305, this was very well done. Clear, concise, right to the point and help me from tearing my hair out.
Absolutely.
Nice to see you back on youtube my man, I always benefit from your videos
Took me a few hours (you go very fast) but got there in the end. Thank you.
This was a terrific video. I understand enough about the Hugo Way (and git) now to follow everything, even though it went quickly. I hope you will do more Hugo stuff because it is awesome.
Nice. That is actually a great way to get around the limitation of Github pages requiring a public repo. I can keep my drafts etc private now. Another option is syncing the public dir with something like copybara.
I got an error message when I first attempted the `git submodule` step at 07:59. The issue was that Hugo had already created a `public` directory for me. I deleted `public` before running the `git submodule` code and everything worked perfectly. Also, Github didn't publish my site instantly like it did for Ryan. I had to wait about 2 minutes before it loaded. But it did load and it looks fantastic. Hope this helps someone. Great video Ryan!
Thanks for the tip! Simply deleting the dir was enough for running git submodule add -b main "URL/public"!
Thank you for the additional info. It did help me.
but in my case , the public dir is not empty is has all the files like index.html , sitemap etc. and i am unable to delete it.
@@adityaranjan3000 Deleting public dir is OK. Look at 8:24, there is nothing except README in the public. Then run '$ hugo server' will re-create all the contents without removing 'README'
@@adityaranjan3000 Because the public folder is generated every time hugo builds a site, you need to delete it before executing the `git submodule` command.
I have seen different ways of doing this, but the simplicity of yours is beautiful. Thanks
true. simple is good.
It took me one and a half days. I almost gave up, and it always led to unexpected errors, but I am satisfied with the result! Thank you for the amazing instructions!
past two weeks I'm struggling to publish my Hugo site . your video helps me a lot
Thanks! I have just followed the process and my blog is live :D It took a bit longer than 10 minutes (Updating homebrew, automating the github pages update with github actions), but a fun journey! Keep up the good content.
Amazing video. Explains all the parts I was struggling with and gives me some good tips!
that submodule trick is geniuss
You might need to run hugo server -D if your posts are not appearing because they are set as drafts.
I tried with the paper theme, but when I deploy the public files github only renders a plain HTML of my project. Any idea what I could have done wrong?
EDIT: figured it out
Messing with the URLs is confusing, you gotta make sure the URL in the config file matches the URL in the generated github page, and any build happens after the changes are saved. Using two repos with similar names, and following a terminal that has a similar name to one of the repos is also confusing. Also, Git is confusing. All that being said, thank you for your tutorial, it was the only one that got it working for me, even if it took me a couple of hours to make it happen.
I am not a very educated person, so I still struggle a lot with these things. However, I would love if in future videos you could find a way to make things more easy to differentiate and avoid confusions for others like me. If not, that is okay too, it is your way of sharing things afterall.
Thank you and have a good day.
Best video on creating a blog period.
Your tutorial is AWESOME! & directly to the point. I followed all the steps except creating two repositories, one where the actual content lives, and one for deployment. I didn't get it why we need 2 different repositories? Speaking of myself, I've created a single repository for the whole process, I found that this is more organized & less error-prone than 2 repositories approach for me.
Could be useful if you have draft posts that you dont want to be in a public repository?
@@natenatters blog repository may be for the draft posts.
Quick and fast tutorial Ryan well done sir will try this out to learn this Hugo thingy.
This was awesome. This channel should be FAR more popular. And I think it soon will be.
Thanks! Been looking for a git module solution with hugo for months!
i really love the clacking of the mechanical keyboard. it makes me feel like i'm in the room with you
Just ran into your channel by typing in hugo tutorial. Not sure if your channel is geared towards beginners or people with coding experience. Great tutorial, love the straightforward, no nonsense approach. My one criticism is it was hard to follow which folder you were typing your commands in with all the cd commands. I think it would be beneficial for you to slow down and reiterate which folder you're in first. I was lost for a bit because I tried to push origin in my public folder but it said it was not a git repo.
Thanks for the vid, didn't know nothing about this git submodule thing until today!
Does anyone know what terminal that is, or what's installed to add that functionality? It's very useful compared to default Terminal in Mac!
I want to ask too!
@@Adso2004-h8d I found the answer. It's called "Oh my ZSH"
Looks like zsh
A lot of topics covered very fast, I learned about submodules and hugo and published my new site. thanks
the most good and straight forward in this topic .. thanks man
oh my god iain from smosh is teaching me hugo
I had a tough time following this vid exactly the way it is. Maybe since I'm using Windows 11... idk. One workaround at 3:17 is inserting 'nano config.toml' and replacing the lines that need to be edited.
This is cool information in the video. But, instead of generating two folders and using git submodule to manage the files, using a github action to generate the static files could be more ergonomic.
thanks for the tutorial, Ryan! just wondering if there are benefits to not also pushing the contents from 'thesimplengineerblog' up to blog repo, to serve as a source control for the raw source code change instead of just having the public repo changelog?
what terminal are you using? looks helpful
could be powerlevel10k
Question on posts. When adding new content like a post do you have to generate a new public folder to push each time?
Yes. Though what I'd do is create a cmd folder with a publish.sh script which would do the build, git add, commit and push for me.
The unread notification is giving me anxieties.
これ見て作ったら本当に10分とちょっとで作れました:)ありがとうございます！！
Thank you X)
英語もできてすげー
Thanks!! This video is so helpful.
Thanks a lot i have created a hugo blog with the help of this tutorial
i really appreciate your video .. thumbs up..
Does the working code repo have to be public? I know the production repo obviously needs to be but can I do this where my "blog" repo is private?
I guess I could try and see what happens! :)
I thought so too!
Did it work?
Where is the config.toml in the directory of the theme file?
hey man I love this tutorial, what terminal are you using? I love it!
It looks to me Ryan was using iTerm with fish shell with tide plugin or similar plugin or iTerm with zsh customized.
The blog doesn't show anything before 2022 and there no entry has matching code.
Why does 404 not found appear after entering the URL given by hugo server?
i have a question though: how do i push future posts onto the repository from terminal? like do i just add the .md file directly into the public folder? then what?
@@coyotewld all this needs to ne done in the repo were we are storing the code right ?
I did the same..... made some changes in my config.toml file and push it to the public repo but there was no change in my production repo (static file that we get)
As this production repo is added as submodule in our public repo so do we need to do something with submodules also to reflect the changes in the production repo ??
We should not add to the public folder directly. We need to move up one folder above the public and add any new posts in to post/yourpost.md then hugo -t again, it will generate the static content corresponding to your new post in to public folder. then you cd to your public folder then push it. It will be reflected on the production site.
@@lifewisdomforu Your comment was helpful!
im not getting github pages but all the files got downloaded into main
help pls
@The Simple Engineer what terminal emulator are you using?
did u forgot to put/commit the blog repository on github? It will be possible to just put a new .md file inside the content folder without having to use hugo again?
Good question. I wonder what is the purpose of having the blog repository.
This video helps me so much
extremely helpful video, though i did have to pause several times and iron out some kinks in my own code (i'm rusty...). thanks a lot for this video, ryan!
I need some help, everytime I put the submodule command, it comes up as 'blog/public' already exists and is not a valid git repo
hey I'm getting the same now, did you ever end up figuring it out?
hi Ryan, just letting you know that the link to your notes (link you mention in the video, and that you left in your description box) is dead. If you could revive it that would be great, in any cases thank you for this very well done video. cheers
Hey sorry about that. Let me try and revive the commands that were embedded in that post
@@TheSimpleEngineer much appreciated, thank you Sir
I think there is no more comliment on this video than just to post "my personal website"(homework) here. I will post it if I success later.
can't post website here, but I summarised this video and would refresh it on my channal
Awesome video! Question: how did you get your CLI to echo the git status?
Good video, it help me so much!!!
nice, finally i can make my hugo site deployed
Your Terminal theme is really nice, would it be possible for you to share your .bashrc ?
with a ton of thanks, the question is: how i could update github content after adding another post maybe? the public folder or blog repo?
go in public folder, git commit and push
blog repo then hugo -t . This will add the new post to the public folder.
Nice Video
Could also apply this for working with Mkdocs. Very helpful video. Thx :)
Thank you so much
wow it worked thanks
Thank you!!
Followed every step, once hosted the site looks completely different. The only difference was I already had a public folder that I deleted and replaced with your method. Also clicking any links gives me a 404... Any suggestions?
I have the same issue. The site renders perfectly locally but when I upload to github it looks like the theme isnt applied and links give me 404 error - did you manage to fix this ?
This fixed it for me
sudo hugo server --theme= --bind=0.0.0.0 --baseUrl= --port=80 --appendPort=false
@@gittin_funky base url in this video was wrong for me updated to use the full url to include my GitHub username and gg
@@LessonsinHistory can you please elucidate, i think i am facing same issue
I think the link is not working
Does anyone knows how to add authentication to a Hugo site?
Thanks for including the link bro! oh wait! you didnt!
wowowow
This is a great video. Currently your website is down. 😞
WOW
对Win10用户可以说是一点都不友好了
Good tutorial but too much of a focus on submodules and Github.
How's live's Github..Juliet still Alive
学会了
this video totally sucks. Tiny text is black background.
thanks