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; } } }

rebuild UI from any directory

jed

During one of the gearup preso's, some gripes were made about having to be in the "customer_src" directory before you can perform a rebuild. That got old really fast for me so I wrote a shell script to get around this issue. Below is a simple shell script that I use to rebuild the UI from any dir on the server. This works on solaris, and it should work on linux and maybe AIX as well. (Is there a TeamSite 6.x for AIX?) As for the windows folks, you are own your own...

Instructions:
1. Copy and paste the code below into a new file on the TeamSite server somewhere such as: $iwhome/local/bin/rebuild-ui.sh
2. chmod 775 <script-name>

#!/bin/sh

# This will rebuild the TeamSite UI from any directory.
# The make_tookit.pl comamnd must be run from the customer_src
# directory which in my opinion is a real pain in the **** and
# not friendly, but that is just one man's opinion.
# Ok--done ranting....

IWHOME=`iwgethome`
cd $IWHOME/local/config/lib/content_center/customer_src
$IWHOME/bin/make_toolkit.ipl

--
Jed Michnowicz
jedm@sun.com
Content Management Engineering
Sun Microsystems

Find more posts tagged with

Comments

gzevin

you probably should capture `pwd`, store it in a variable and cd back to it after make_toolkit. This will make the script simply indispensable

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

jed

After running the script, you should be in the same directory as where you started, or at least that has been my experience. But keeping storing pwd and cd'ing back would be a good enhancement. Something like this (untested):

CWD=`pwd`
IWHOME=`iwgethome`
cd $IWHOME/local/config/lib/content_center/customer_src
$IWHOME/bin/make_toolkit.ipl
cd $CWD

--
Jed Michnowicz
jedm@sun.com
Content Management Engineering
Sun Microsystems

gzevin

brilliant! Smiley Happy

such little things make us very happy!

It wonders me why this has not been done by IWOV (or, as a matter of fact, why make_toolkit.ipk should have this functionality built in).

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

Adam Stoller

I had a discussion with Brinko about this while attending GearUp - and the rationale for not hard-coding a default starting location in make_toolkit.ipl went something along these lines:

There may be (either via customers or via Interwoven itself in the future) other toolkits than content_center - so hardcoding to default to content_center may cause problems if/when that situation arises
If you store your tookit somewhere other than IWHOME/local/config/lib/content_center/customer_src (e.g. some folks store all that information within TeamSite and do the builds directly from a workarea), then the hard-coded default could cause problems

(there may have been one or two other points, can't remember right now).

Some of the things that I clarified about the idea was that:

It should only use the hard-coded default if
- there was no -src flag provided
- the current directory (.) doesn't contain the expected directory structure for a toolkit

We talked about it some more - and he seemed to think that perhaps it could reference an environment variable - which, if set and the conditions I just stipulated above were considered - would then use the value from that environment variable.

I don't know if that will ever happen (I'm not sure I'd classify this as anything other than a "low priority" nuisance) - so the posted script suggestion is probably a good way to go (I do something similar as part of a DNR script for OD which I use to push my versioned customization files from TS to the local disk)

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

gzevin

yes, at least good with the given restrictions.

thanks for the update.. it's a shame I could not come for GearUp

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