Suggestion: build_include.txt

[SimonWpt]

I am often working on websites with a lot of pages AND static files in root dirctory. It would be nice to move these files to an include directory and copy them only when building. These static files are only necessary for the build but not for working with fire.app.

Some examples:

google123456789123456789.html
y_key_123456789123456789.html
BingSiteAuth.xml
sitemap.xml
robots.txt
.htaccess
favicon.ico
touch-icon-iphone.png
touch-icon-ipad.png
touch-icon-iphone-retina.png
touch-icon-ipad-retina.png
backup/*
downloads/*.zip
documents/*.pdf
gallery/*.jpg
text/*.txt

It would be great, if I could create a build_include.txt (similar to build_ignore.txt). We could add all files and directories, we wished to copy from the include directory to the root directory.

This feature makes it very easy to keep the overview. At the moment I do this task on some projects with grunt, but fire.app would be the better solution.

[hlb]

@SimonWpt what is the problem if you just put them in the project folder directly?

[SimonWpt]

@hlb There is no problem, it is just easier to navigate in tree. In most IDE (like Aptana) you have a treeview and see all files in the documentroot and all root directories (and collapsed directories and files). Everytime, I look on the treeview, I see a lot of files, which are created once and then will never be touched again.

Here is an one-page example:

[.coffeescript-cache]
[.sass-cache]
[coffeescripts]
[css]
[documents]
[downloads]
[fonts]
[haml]
[images]
[js]
[sass]
.htaccess
6543210987654321ABCDEF_Y.txt
BingSiteAuth.xml
compress.php
favicon.ico
google6543210987654321.html
google1234567890123456.html
index.html.haml
robots.txt
sitemap.xml
touch-icon-iphone.png
touch-icon-ipad.png
touch-icon-iphone-retina.png
touch-icon-ipad-retina.png
y_key_6543210987654321.html

This is the version, where all static files are moved to the directory [.includes]:

[.coffeescript-cache]
[.sass-cache]
[.includes]
[coffeescripts]
[css]
[haml]
[images]
[js]
[sass]
index.html.haml

Most IDE has treeview for navigating. You see the difference, in the first example I have to search the index.html.haml in a bulk of 14 files, in the second example there is only one file, the index.html.haml.

In the second example I have moved the directories [documents], [downloads] and [fonts] to [.includes]. All these files are created once and then I can forget them.

I hope, you understand the reason, why I would prefer an include directory.

[hlb]

@SimonWpt We have strongly considered to add build hook, so you can execute some commands before or after "build project". It seems also work in your case.

[SimonWpt]

OK. Where can I find the doc about adding build hooks?

[hlb]

@SimonWpt not done yet ;)

[hlb]

ref: #174. close this one.