On 27/05/14 23:37, Kay Schenk wrote: > > > On 05/27/2014 01:30 PM, Marcus (OOo) wrote: >> @Joe: >> See my last my mail. >> >> Lesson learned: >> I've just seen what was updated in my workspace. But there is no hint >> that other commits will be taken into account, too. Until you open this >> link: >> https://cms.apache.org/ooo-site/publish?diff=1 >> >> As here the truth is shown. >> >> So finally, believe in your admin or burn in hell. :-) >> >> Marcus > > Well maybe not burn in hell, but at least gain some truth. Reviewing > this "diff" can be is very important at times. :)
I think it is a bad design that even minor changes on one page trigger a complete update of the whole site. It might scale for smaller project with only a few pages and less changes. But it doesn't scale for large projects as AOO where many people in different areas would like to work on changes without conflicting with other changes. The question is if this is really state of the art or if a free alternative would make more sense and would reduce in the end the maintenance work. I am sure their were valid reason for the CMS in the past but I believe today better tools are in place where more than 1 man stand behind. Well it's just my personal opinion and I don't really propose a change ;-) I just wondering and asking this question myself whenever I have to make a simple change. Juergen > >> >> >> >> Am 05/19/2014 11:56 PM, schrieb Joe Schaefer: >>> I think there's some confusion about what is actually happening >>> when you click on the Update link in the webgui. All that does >>> is run >>> >>> % svn up /path/to/underlying/svn/resource >>> >>> on the CMS server. When you publish you are essentially doing >>> >>> % svn rm >>> https://svn.apache.org/repos/infra/websites/production/ooo-site/content >>> % svn cp >>> https://svn.apache.org/repos/infra/websites/staging/ooo-site/trunk/content >>> https://svn.apache.org/repos/infra/websites/production/ooo-site/content >>> >>> >>> but in a single-step using svnmucc. >>> >>> That's all the webgui does- it's just a wrapper around the underlying >>> svn commands. What you are working with in the webgui is an svn >>> checkout of the site. "Update" just brings your current checkout up >>> to date within the portion of the tree that you are browsing. >>> >>> HTH >>> >>> >>> On Monday, May 19, 2014 3:44 PM, Marcus (OOo)<marcus.m...@wtnet.de> >>> wrote: >>> >>> >>>> >>>> >>>> Am 05/19/2014 09:20 PM, schrieb Joe Schaefer: >>>>> Sorry but technically the CMS publishes all committed >>>>> changes to the staging site. The only way to partition >>>>> changes is to partition your commits. >>>> >>>> >>>> but which data will be published: the content of the SVN repository or >>>> the content of the personal CMS work space? >>>> >>>> I guess the work space as I need to update it with the SVN content. >>>> Otherwise there is nothing new to publish. >>>> >>>> Thanks >>>> >>>> Marcus >>>> >>>> >>>> >>>> >>>>>> On Monday, May 19, 2014 3:17 PM, Marcus >>>>>> (OOo)<marcus.m...@wtnet.de> wrote: >>>>>>> Am 05/19/2014 09:51 AM, schrieb Andrea Pescetti: >>>>>>> On 29/04/2014 Marcus (OOo) wrote: >>>>>>>> The main point is *where you are* in the CMS Browse View when >>>>>>>> you click >>>>>>>> on the "Update" link. >>>>>>> >>>>>>> I tried several times, but I'm not sure it works for me. Maybe >>>>>>> it works >>>>>>> if we see "update" as "update this directory". >>>>>>> >>>>>>>> Example to update and publish only a file: >>>>>>>> 1. In your browser open, e.g., >>>>>>>> "www.openoffice.org/my-dir/my-subdir/index.html". >>>>>>>> 2. Open the CMS via the bookmarklet. >>>>>>>> 3. Click on the link "[Edit]" in the row of the >>>>>> "index.html" file. >>>>>>>> 4. Click on the link "[Update]". >>>>>>>> 5. Do your changes in the file. >>>>>>>> 6. Commit your changes. >>>>>>>> 7. On the following page click on the link "[Publish]". >>>>>>> >>>>>>> In the last days I tried to do this for the main index.html >>>>>>> page and for >>>>>>> the download/devbuilds.html page. I commit to SVN directly (so >>>>>>> I don't >>>>>>> use the CMS for editing pages), but the rest works as you >>>>>>> describe. So I >>>>>>> browse to download/ in the CMS and when I update it downloads >>>>>>> my changed >>>>>>> devbuilds.html page and nothing else. But then, when I >>>>>>> publish, if I >>>>>> >>>>>> Then you have update the *complete directory* but *not the single >>>>>> file*. >>>>>> >>>>>> OK, I'll do it again: >>>>>> >>>>>> 1. Open w.oo.o/index.html >>>>>> 2. Login via CMS bookmarklet >>>>>> 3. Click on [Edit] in the row for "index.html" >>>>>> 4. Click on [Update] on the top >>>>>> 5. Only this file was updated >>>>>> 6. >>>>>>> click "View diff" I see all the changes in "download". >>>>>>> >>>>>>> So maybe committing through SVN means that I'm forced to >>>>>>> update the >>>>>>> directory, and thus if I change the main index.html file I >>>>>>> must publish >>>>>>> the whole site, and if I change devbuilds.html I must publish >>>>>>> the whole >>>>>>> subtree (download/) containing it? In that setup, indeed I >>>>>>> wasn't able >>>>>>> to find a command like "Update this file only". >>>>>> >>>>>> No, SVN is outside of this. I do it like you. It's like I wrote on >>>>>> the top: >>>>>> >>>>>> The main point is *where you are* in the CMS Browse View when you >>>>>> click >>>>>> on the "Update" link. >>>>>> >>>>>> That means: >>>>>> When you are in a directory, e.g., "download/" and click on >>>>>> "Update" >>>>>> then you get every new thing of this directory. >>>>>> >>>>>> But when a single file, e.g., "devbuild.html" is shown and you click >>>>>> on >>>>>> the "Update" link then only this file is updated and nothing else. >>>>>> >>>>>> Please can you try it and confirm? >>>>>> >>>>>> Thanks >>>>>> >>>>>> >>>>>> Marcus >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
