How can I stop "jekyll build" from overwriting existing files in the output directory?

Question

The source for my Jekyll-powered website lives in a git repo, but the website also needs to have a couple large static files that are too large to go under version control. Thus, they are not part of the Jekyll build pipeline.

I would like for these to simply live in an assets directory in the Jekyll destination (which is a server directory; note that I don't have have any control over the server here; all I can do is dump static files into a designated directory) that does not exist in the git repo. But, running jekyll build deletes everything in the output directory.

Is there a way to change Jekyll's behavior in this case? Or is there some other good way to handle this issue?

These are bioinformatics datasets (and some old software that was released as ZIP files). — jveldridge, Jan 23 '14 at 19:22
Can't you just create a different folder and have jekyll just copy it over during the build phase? — Noah Clark, Jan 23 '14 at 19:49
That's not ideal since some of the files in question are sufficiently large that copying them is slow. But, if there's no better solution, that may be what we have to do. — jveldridge, Jan 23 '14 at 21:11

score 4 · Answer 1 · edited May 23 '17 at 12:26

4

Not sure this addresses the specific case in the OP, but seeing as how I kept getting to this page when I finally found an answer here, I thought I'd add an answer to this question in case it helps others.

I have a git post-hook that builds my jekyll site in my webhost when I push to my host, but it was also deleting anything else that I had FTP'ed over. So now I've put anything I need to stick around in a directory (external/ in my case), and added the following to my _config.yml:

exclude: [external]
keep_files: [external]

and now files in external/ survive.

edited May 23 '17 at 12:26

Community

1
1

answered Aug 02 '16 at 20:00

Max Starkenburg

1,499
1
15
21

1

This is the right answer. [`keep_files`](https://jekyllrb.com/docs/configuration/options/) is specifically to avoid deleting files on the output directory. – fregante Apr 28 '20 at 10:58

score 3 · Accepted Answer · edited May 23 '17 at 12:18

If you upload Jekyll's output directory via FTP to your server, you can use a FTP tool that lets you ignore folders.

For example, my own site is built with Jekyll, but hosted on my own webspace, so I'm uploading it via FTP.
I explained in this answer how I scripted the building and uploading process, so I can update my site with a single click.

In my case (Windows), I used WinSCP, a free command-line FTP client, for this.
If you're not on Windows, you need to use something else, but there are probably other FTP tools out there that are able to ignore folders.

To ignore your assets folder in WinSCP, you just need to put this line into the script file:
(the file which contains the actual WinSCP commands - read my other answer for more information)

option exclude "assets/"

Now you can upload your large assets folder on the server once, and it won't be overwritten/deleted when you later update your site via FTP.

How can I stop "jekyll build" from overwriting existing files in the output directory?

2 Answers2