"output_dir" config option being ignored on 0.5.0 about punch HOT 12 CLOSED

I tried to re-create the issue by setting up a new site with 0.5.0. But it picks the output_dir setting correctly. Are you sure the project being generated with 0.5.0?

Also, can you try to run punch g after deleting the existing output directory?

from punch.

I don't think the project was generated with 0.5.0, more likely 0.4.? but have tried deleting both public and output dir's and punch g recreates the output dir.

from punch.

I actually meant the version currently used to generate the output. You can find it by running punch -v inside the project's directory.

Also, could you create a new site with Punch and see whether this issue occurs in it as well?

from punch.

Yes punch -v returns 0.5.0.

I'm away from my machine at the moment (replying on phone) so will try a new project in the morning but I'm guessing there will be the same issue as it's only the config.json file that affects this, right?

from punch.

I'm not sure whether a different local installation of Punch is being used to generate the site in this instance, instead of the global version. That's why I said it would be better to test by creating a new site.

from punch.

New project works fine which is weird as punch -v is returning 0.5.0 wherever I run it. I have no node_modules directory in the problem project so I can't see how it is any different running punch g there vs a new project. Very odd... does it create some hidden files that I don't know about?

from punch.

No. it doesn't create any hidden files other than the .last_published file.

Are there two config files (or a config directory) by any chance?

from punch.

Also removed all old versions i.e. 0.3.? and 0.4.? from ~/.npm and still got same issue.

from punch.

I should probably mention that I have a couple of extra files at the root of the folder for deployment i.e. config/deploy.rb, lib/tasks/vlad.rake and Rakefile but can't see how this would affect anything.

from punch.

The problem is caused by the config directory you're having for deploy.rb. Punch will give priority to config directory and then only move on to use the config.json file.

In this case it assumes your configurations are stored in the directory. Since they are not there it resorts to default. Can you try renaming the existing config directory? It should work.

from punch.

Thanks, that does in fact solve the problem however isn't it a bad idea for punch to reserve the entire config directory?

I use Vlad, the deployment rubygem and it expects a deploy.rb file to exist in the config directory.

from punch.

True. I pushed a fix which uses the config.json file if it exists, ignoring the config directory. Try installing the version 0.5.1.

Also, it's possible to give the config file path explicitly. In that case, the generate command should run this way: punch g config.json

from punch.