nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

data directory structure (automated?)

DavidMusser

Does anyone have any scripts to automate the creation of sub directories in the data directory to mirror production.

I would like to have something that would run on a semi regular basis to add sub directories to the data directory for dcr storage.

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

Find more posts tagged with

Comments

Adam Stoller

This seems a bit backwards - shouldn't production mirror the source as opposed to the other way around? I.e. how did the directories get on production if they didn't original at the source?

Clearly there are numerous ways that one could approach this - but I don't have anything pre-written to provide.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

DavidMusser

Conversion of an existing site into TeamSite. Moving from Static Pages to templates. So the directory structure already exists for the output, was just thinking about segmenting the generic template that could do a lot of the site by directory structure.

The problem is that If a new dir gets created in the html directory I need to verify that it's created in the data directory etc.

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

Adam Stoller

Assuming a consistancy between directories in the docroot of the website and the data directory in TeamSite - you could have a script run from the docroot to generate a list of all the directories there, and then take that list with another script and have it verify that all those directories exist under the data directory in TeamSite.

If you're really into it - you could probably write it as a client-server program - or you might be able to do it via some sort of OpenDeploy DNR script process.

As long as you ensure that the list of directories is presented *relative* to the docroot it should be pretty simple.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

gzevin

I wrote a lots of stuff similar to this... but usually it's other way around. we create a directory in a DCR tree and then a workflow replicates it in the web site structure

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU