# After using 'hugo server' do I need to run 'hugo' before deploying?

**URL:** <https://discourse.gohugo.io/t/after-using-hugo-server-do-i-need-to-run-hugo-before-deploying/601>\
**Category:** support\
**Created:** [January 17, 2015, 10:42pm UTC](https://discourse.gohugo.io/t/after-using-hugo-server-do-i-need-to-run-hugo-before-deploying/601 "2015-01-17T22:42:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Smith](https://avatars.discourse-cdn.com/v4/letter/d/a3d4f5/32.png) [@David\_Smith](https://discourse.gohugo.io/u/David_Smith)\
**Post date:** [January 17, 2015, 10:42pm UTC](https://discourse.gohugo.io/t/after-using-hugo-server-do-i-need-to-run-hugo-before-deploying/601/1 "2015-01-17T22:42:56Z")

</div>

After I’ve run ‘hugo server’ the links in the output/public folder rendered files have absolute links to localhost:1313… so I then need to run just ‘hugo’ before deploying.

Is this the expected behaviour or should my output folder contain the correct links after using ‘hugo server’?

---

<div class="post-metadata">

**Author:** ![anthonyfok](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/anthonyfok/32/106_2.png) [@anthonyfok](https://discourse.gohugo.io/u/anthonyfok)\
**Post date:** [January 17, 2015, 10:54pm UTC](https://discourse.gohugo.io/t/after-using-hugo-server-do-i-need-to-run-hugo-before-deploying/601/2 "2015-01-17T22:54:02Z")

</div>

Hi @David_Smith,

Yes, you need to stop `hugo server`, and run just `hugo` to have the proper absolute URLs generated before deploying. 🙂

Cheers,  
Anthony

---

<div class="post-metadata">

**Author:** ![anthonyfok](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/anthonyfok/32/106_2.png) [@anthonyfok](https://discourse.gohugo.io/u/anthonyfok)\
**Post date:** [January 18, 2015, 10:05am UTC](https://discourse.gohugo.io/t/after-using-hugo-server-do-i-need-to-run-hugo-before-deploying/601/3 "2015-01-18T10:05:45Z")

</div>

Hi again @David_Smith!

You may find this interesting. Hugo’s author @spf13 had this to say in his post at [http://discuss.gohugo.io/t/hugo-refactor/283:](http://discuss.gohugo.io/t/hugo-refactor/283:)

> I also want to have a feature where `hugo server` doesn’t write the destination files to disk, but instead saves it in memory and serves from there. It actually works right now if you just comment out the last line in the hugofs/fs.go file. Using the memory backed filesystem improves build times around 10% according to my rough benchmarks. Yup. Hugo can get even faster.

---

<div class="post-metadata">

**Author:** ![dhersam](https://avatars.discourse-cdn.com/v4/letter/d/c5a1d2/32.png) [@dhersam](https://discourse.gohugo.io/u/dhersam)\
**Post date:** [January 21, 2015, 9:08pm UTC](https://discourse.gohugo.io/t/after-using-hugo-server-do-i-need-to-run-hugo-before-deploying/601/4 "2015-01-21T21:08:34Z")

</div>

Wow, that would be a great usability addition (I’ve forgotten to run `hugo` several times after using `hugo server`), but the speed increase alone would be worth it. The faster the better 🙂