Support for Directories in Export folder

[MichaelRBond]

The number of Exports are starting to get unwieldy.

Add support for directories.

If a directory exists, start a new unordered list element. All PHP files under it will follow the same naming rules as files in the parent directory and be listed with li elements in the parent UL

[jmm0177]

Tracy-- will you take a look at this?

[trmccormick]

Sure

On Oct 17, 2016 12:33 PM, "jetapia" [email protected] wrote:

Tracy-- will you take a look at this?

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
#224 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQIDS6GDwAwbxoC2qb02Wmykdp7ocZsSks5q06N3gaJpZM4Ix-xk
.

[trmccormick]

Sure

On Oct 17, 2016 12:33 PM, "jetapia" [email protected] wrote:

Tracy-- will you take a look at this?

—
You are receiving this because you were assigned.

Reply to this email directly, view it on GitHub
#224 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQIDS6GDwAwbxoC2qb02Wmykdp7ocZsSks5q06N3gaJpZM4Ix-xk
.

[MichaelRBond]

When you do this, you will need to also change how the mfcs-exports repository is structured.

That repository is git pulled to the server and put in place with symlinks. All of those symlinks will need to be updated. Also, this will affect the sym links were the actual export data is being stored. (potentially).

I would HIGHLY recommend that instead of doing all those symlink changes by hand that you write an ansible script to handle the changes for you. that way, when there are new exports too setup, the ansible script can be updated and re-run to ensure everything is correct/set ... and will lead to an easier, more consistent way to handle these updates in the future.