# Merge Jekyll with existing Apache site
**URL:** https://talk.jekyllrb.com/t/merge-jekyll-with-existing-apache-site/2390
**Category:** Help
**Created:** [December 4, 2018, 10:15am UTC](https://talk.jekyllrb.com/t/merge-jekyll-with-existing-apache-site/2390 "2018-12-04T10:15:12Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@johann-petrak](https://talk.jekyllrb.com/u/johann-petrak)
#### Post date: [December 4, 2018, 10:15am UTC](https://talk.jekyllrb.com/t/merge-jekyll-with-existing-apache-site/2390/1 "2018-12-04T10:15:12Z")
I really love how Jekyll makes a lot of nice things available and would love to migrate a rather large site to Jekyll.
That would be a considerable effort and could only be done for a small number of pages quickly.
What I would therefore like to do is this:
- use Jekyll for the small number of pages: so some existing URLs and some new URLs would get served by Jekyll
- have some mechanism to show all other URLs from the “OLD” site.
Is there a standard mechanism for doing this?
---
### Author:  [@mmistakes](https://talk.jekyllrb.com/u/mmistakes)
#### Post date: [December 4, 2018, 1:30pm UTC](https://talk.jekyllrb.com/t/merge-jekyll-with-existing-apache-site/2390/2 "2018-12-04T13:30:52Z")
Jekyll doesn’t serve anything. It simply generates “final” HTML files that you can host as you like.
There’s no reason why you couldn’t build the new pages with Jekyll, deploy to your hosting server, and leave the old pages.
---
### Author:  [@johann-petrak](https://talk.jekyllrb.com/u/johann-petrak)
#### Post date: [December 4, 2018, 2:52pm UTC](https://talk.jekyllrb.com/t/merge-jekyll-with-existing-apache-site/2390/3 "2018-12-04T14:52:44Z")
Thanks!
So far, I use Jekyll to serve a site using the “bundle exec jekyll serve” command, but I understand I could use it to just generate the pages.
What are the advantages of serving a Jekyll generated site using Jekyll versus using something like Apache? Are there any?
---
### Author:  [@rdyar](https://talk.jekyllrb.com/u/rdyar)
#### Post date: [December 4, 2018, 4:46pm UTC](https://talk.jekyllrb.com/t/merge-jekyll-with-existing-apache-site/2390/4 "2018-12-04T16:46:28Z")
> [@johann-petrak](#):
>
> What are the advantages of serving a Jekyll generated site using Jekyll
the server that is bundled with jekyll is a development server really - while it may work in a production environment, it is not recommended I don’t think - it is just there to help you while doing development. Apache would be better, though not sure I could point out the reasons why for a single site.
---
### Author:  [@mmistakes](https://talk.jekyllrb.com/u/mmistakes)
#### Post date: [December 4, 2018, 4:58pm UTC](https://talk.jekyllrb.com/t/merge-jekyll-with-existing-apache-site/2390/5 "2018-12-04T16:58:33Z")
To my knowledge Jekyll uses [WEBrick](https://ruby-doc.org/stdlib-2.0.0/libdoc/webrick/rdoc/WEBrick.html) for the development server.
There’s probably some resources around with comparisons between it and a production server like Apache. For example [this thread](https://stackoverflow.com/questions/4113299/ruby-on-rails-server-options) on Stackoverflow.
---
### Author:  [@TerminalAddict](https://talk.jekyllrb.com/u/TerminalAddict)
#### Post date: [December 5, 2018, 1:47am UTC](https://talk.jekyllrb.com/t/merge-jekyll-with-existing-apache-site/2390/6 "2018-12-05T01:47:55Z")
memory management, multi-threading, proper 404/502 handling, security, stability
The list is quite long … don’t use jekyll serve in production.
Use a production http server (Apache, nginx, lighthttpd … even _gasp_ iis _gasp_ )