Skip to content
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

Option for running a server #14

Closed
silvenon opened this issue Sep 5, 2013 · 12 comments
Closed

Option for running a server #14

silvenon opened this issue Sep 5, 2013 · 12 comments
Milestone

Comments

@silvenon
Copy link

silvenon commented Sep 5, 2013

It would be nice if guard-nanoc would have an option for running a server, so I don't have to run nanoc view as a separate process.

@denisdefreyne
Copy link
Member

nanoc view is removed in nanoc 4.0 because it’s pretty redundant. Alternatives:

  • Run adsf manually;
  • Set up a web server to serve the output directory. On Mac OS X, this is trivial with Anvil, which I now use all the time.

I’m inclined to say that an option for running a server is not needed, and that a different approach should be recommended (I really like Anvil/pow).

@bobthecow Thoughts?

@bobthecow
Copy link
Contributor

@ddfreyne The one upside to a server is for teh n00bs, and people who don't care to set up an entire ecosystem of stuff just to run an SSG. It's a lot easier to say "run nanoc server and go to localhost:3000".

@silvenon
Copy link
Author

silvenon commented Sep 5, 2013

Yeah, I would really like that.

@bbakersmith
Copy link

I also think this would be nice to have as an option for guard-nanoc. It's not that it's hard to use a dev server gem like adsf or heel directly, but standardizing the process across nanoc projects + developers and decreasing the number of tmux panes I have to keep open has its benefits.

@bobthecow
Copy link
Contributor

having a nanoc-server gem (and accompanying nanoc server command) which just started adsf on the output directory and ran guard-nanoc would probably be enough?

@bbakersmith
Copy link

Yeah that seems like it'd do the trick, don't need anything fancy.

@denisdefreyne
Copy link
Member

Perhaps an --autobuild option to a nanoc serve command would work. I’m inclined to say that nanoc serve (or nanoc view or whatever) should not run Guard by default, because that means the serve command cannot be used without Guard, which is possibly not ideal.

Invoking guard programmatically seems simple (Guard.setup and Guard.run_all).

@bobthecow
Copy link
Contributor

I'd do it without the flag. People who don't want the jekyll server experience don't need to install nanoc-serve. This is for people who want a more packaged, easier setup.

@denisdefreyne
Copy link
Member

Makes sense. They could just run adsf -r output :)

@mpapis
Copy link
Contributor

mpapis commented Sep 5, 2014

related #15

@whitequark
Copy link
Contributor

#28

@denisdefreyne denisdefreyne modified the milestone: 2.1.0 Jul 13, 2016
@denisdefreyne
Copy link
Member

The nanoc live command (part of guard-nanoc 2.1.0) now covers this case!

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

No branches or pull requests

6 participants