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

Managing TeamSite configuration files

System

We would like to be able to manage TeamSite's configuration files from within a TeamSite sub-branch, particularily to store version history and avoid the need to log onto the server directly.

We are planning to do the following:
1) create a new 'admin' branch within default/main/
2) create a new WORKAREA named 'shared'
3) import specific files and folders from /.software/TeamSite on the Unix server into the WORKAREA
4) set up OpenDeploy to deploy the files to /.software/TeamSite on the TeamSite server itself.

Are there any specific config files we should not manage, or are not going to be able to manage within TeamSite by following this approach?.

I presume we will end up adjusting the default permissions set on any config files and would welcome any advice on this topic.

Find more posts tagged with

Comments

jagadesh

We would like to be able to manage TeamSite's configuration files from within a TeamSite sub-branch, particularily to store version history and avoid the need to log onto the server directly.

We are planning to do the following:
1) create a new 'admin' branch within default/main/
2) create a new WORKAREA named 'shared'
3) import specific files and folders from /.software/TeamSite on the Unix server into the WORKAREA
4) set up OpenDeploy to deploy the files to /.software/TeamSite on the TeamSite server itself.

Are there any specific config files we should not manage, or are not going to be able to manage within TeamSite by following this approach?.

I presume we will end up adjusting the default permissions set on any config files and would welcome any advice on this topic.

You can manage the below folder files under Teamsite Workarea, create workflow to update these files from workarea to /iw-home

OD-home/conf
OD-home/userlib if any custom OD classes
OD-home/etc
TShome/local/config
TShome/httpd/iw-bin/{custom Folder}
TShome/iw-perl/site/lib/ if any custom modules are present

nipper

A common approach, very good idea. It does get more complicated. You have to consider dev server or prod server, then how are you getting files from dev to prod. Most of the files will move straight from one server to another, but osnode, odbase, iw.cfg, and other cannot be moved. If you use livesite, it gets more complex.

I did a GearUp presentation on this topic, you may be able to search (Enterprise adoption of Teamsite) for the slides or ping me off line.

I am still working on a better way to handle LiveSite. Unfortunately some of the tools IWOV provides (build.bat, OD GUI, iw.cfg edit screen) want to work on the iwhome/odhome copy and not on a config branch

HTH

Andy

Migrateduser

You can manage the below folder files under Teamsite Workarea, create workflow to update these files from workarea to /iw-home
OD-home/conf
OD-home/userlib if any custom OD classes
OD-home/etc
TShome/local/config
TShome/httpd/iw-bin/{custom Folder}
TShome/iw-perl/site/lib/ if any custom modules are present

Why only these???

jagadesh

Why only these???

Its just Sample. These are files we will modify frequently for the functionality implementation whenever requires.

Migrateduser

Its just Sample. These are files we will modify frequently for the functionality implementation whenever requires.

A fine example of how to not be helpful. You make it seem like those are the only config files that can be managed by TeamSite. Think before you write.

jagadesh

A fine example of how to not be helpful. You make it seem like those are the only config files that can be managed by TeamSite. Think before you write.

Thanks for your valuable comments

Migrateduser

Thanks for your valuable comments

You're welcome! I hope they help! :rolleyes: