2008/11/11 Frederic Hemberger <[EMAIL PROTECTED]>
>
> If you change your publication target for example (from hoster A to
> hoster B)
We're incredibly unlikely to ever change domain name, and pretty unlikely to
change host. I believe there will be many other issues if we ever DO do
that, and checking out CSS files from a repository seems far easier to me
than configuring RedDot to publish to a new host, and publishing everything
out.
> or create a new child project which depends on the content
> classes
I don't quite understand what you're referring to here. What's a 'child
project'? Our CSS files are structured in such a way that the content
classes are single-use anyway (e.g. they're just a template containing all
the CSS, the actual instance ('page' in RD terminology) itself contains very
little, if any, data).
> Especially in complex corporate projects, having multple souces of
> data can really be a mess:
Yeah, I wouldn't want multiple copies of the same files, more some files in
svn, some managed by RedDot.
> on server A (e.g. live environment), not server B (DEV system), and so
> on. Even with a SCS system, this can easily happen (there is always
> that ONE guy who manages it to get past it *g*).
>
You overestimate our development enviornment! :-) There's no dev system,
there's *only* one guy.
> Same is true if you are working with RedDot LiveServer: Of cause you
> can edit/develop the dynament code directly in the LiveServer
> repository, then something happens to the project (files get
> overwritten, corrupt database, a different code revision gets
> published, whatever) and you're really screwed.
Don't worry - I don't go anywhere near LS!
- Bobby
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"RedDot CMS Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/RedDot-CMS-Users?hl=en
-~----------~----~----~----~------~----~------~--~---
