migrating the main site to the CMS- a simple approach
|
View:
New views
16 Messages
—
Rating Filter:
Alert me
|
 |
migrating the main site to the CMS- a simple approach
by Joe Schaefer-6
::
Rate this Message:
So I realize that I don't have enough time myself
to convert the incubator site's content to markdown even tho there are scripts to automate that process. Instead let me offer a different idea- to keep the existing build system but superimpose the CMS on top of it. To facilitate this, all that needs to happen is for someone to find a generic way of invoking anakia so it satisfies the command-line interface of https://svn.apache.org/repos/infra/websites/cms/build/build_external.pl (ie builds sources from ./content/ into a specified target dir). By generic, I mean a suitable command-line invocation for the build_external.pl script for the "anakia" type (basically supplying the right @system_args in the script) so that pretty much any site currently using anakia will be able to do the same thing. Hopefully the challenge to produce such @system_args is within the means of this community ;-)- it amounts to 1 line of perl at this point. |
|
|
Re: migrating the main site to the CMS- a simple approach
by sebb-2-2
::
Rate this Message:
On 14 February 2012 16:21, Joe Schaefer <joe_schaefer@...> wrote:
> So I realize that I don't have enough time myself > to convert the incubator site's content to markdown > even tho there are scripts to automate that process. > Instead let me offer a different idea- to keep the > existing build system but superimpose the CMS on top > of it. > To facilitate this, all that needs to happen is for > someone to find a generic way of invoking anakia so > it satisfies the command-line interface of > > https://svn.apache.org/repos/infra/websites/cms/build/build_external.pl > > (ie builds sources from ./content/ into a specified target > dir). That's not actually sufficient to build the main Incubator site, because it does not take the Clutch updates into account. However, I guess Clutch could be run separately to update the source files, and then trigger a site rebuild. > By generic, I mean a suitable command-line invocation > for the build_external.pl script for the "anakia" type > (basically supplying the right @system_args in the script) > so that pretty much any site currently using anakia will > be able to do the same thing. > > Hopefully the challenge to produce such @system_args is > within the means of this community ;-)- it amounts to > 1 line of perl at this point. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by Joe Schaefer-6
::
Rate this Message:
>________________________________
> From: sebb <sebbaz@...> >To: general@... >Sent: Tuesday, February 14, 2012 11:57 AM >Subject: Re: migrating the main site to the CMS- a simple approach > >On 14 February 2012 16:21, Joe Schaefer <joe_schaefer@...> wrote: >> So I realize that I don't have enough time myself >> to convert the incubator site's content to markdown >> even tho there are scripts to automate that process. >> Instead let me offer a different idea- to keep the >> existing build system but superimpose the CMS on top >> of it. > >> To facilitate this, all that needs to happen is for >> someone to find a generic way of invoking anakia so >> it satisfies the command-line interface of >> >> https://svn.apache.org/repos/infra/websites/cms/build/build_external.pl >> >> (ie builds sources from ./content/ into a specified target >> dir). > >That's not actually sufficient to build the main Incubator site, >because it does not take the Clutch updates into account. > >However, I guess Clutch could be run separately to update the source >files, and then trigger a site rebuild. Ideally the Clutch updates can be considered as "dynamic content" for the CMS, so we can simply schedule clutch builds on a periodic basis. That is done separately from the generic process of doing anakia builds. > >> By generic, I mean a suitable command-line invocation >> for the build_external.pl script for the "anakia" type >> (basically supplying the right @system_args in the script) >> so that pretty much any site currently using anakia will >> be able to do the same thing. >> >> Hopefully the challenge to produce such @system_args is >> within the means of this community ;-)- it amounts to >> 1 line of perl at this point. > >--------------------------------------------------------------------- >To unsubscribe, e-mail: general-unsubscribe@... >For additional commands, e-mail: general-help@... > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by Joe Schaefer-6
::
Rate this Message:
----- Original Message -----
> From: Joe Schaefer <joe_schaefer@...> > To: "general@..." <general@...> > Cc: > Sent: Tuesday, February 14, 2012 12:04 PM > Subject: Re: migrating the main site to the CMS- a simple approach > >> ________________________________ >> From: sebb <sebbaz@...> >> To: general@... >> Sent: Tuesday, February 14, 2012 11:57 AM >> Subject: Re: migrating the main site to the CMS- a simple approach >> >> On 14 February 2012 16:21, Joe Schaefer <joe_schaefer@...> > wrote: >>> So I realize that I don't have enough time myself >>> to convert the incubator site's content to markdown >>> even tho there are scripts to automate that process. >>> Instead let me offer a different idea- to keep the >>> existing build system but superimpose the CMS on top >>> of it. >> >>> To facilitate this, all that needs to happen is for >>> someone to find a generic way of invoking anakia so >>> it satisfies the command-line interface of >>> >>> https://svn.apache.org/repos/infra/websites/cms/build/build_external.pl >>> >>> (ie builds sources from ./content/ into a specified target >>> dir). >> >> That's not actually sufficient to build the main Incubator site, >> because it does not take the Clutch updates into account. >> >> However, I guess Clutch could be run separately to update the source >> files, and then trigger a site rebuild. Alternately, if the clutch builds simply modify source content, that aspect can be performed manually and the build system will generate that content from the changes to the source content. All someone would have to do in addition to what they already already do now is publish the changes to the live site. > > > Ideally the Clutch updates can be considered as "dynamic content" for > the CMS, so we can simply schedule clutch builds on a periodic basis. > That is done separately from the generic process of doing anakia builds. > > >> >>> By generic, I mean a suitable command-line invocation >>> for the build_external.pl script for the "anakia" type >>> (basically supplying the right @system_args in the script) >>> so that pretty much any site currently using anakia will >>> be able to do the same thing. >>> >>> Hopefully the challenge to produce such @system_args is >>> within the means of this community ;-)- it amounts to >>> 1 line of perl at this point. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscribe@... >> For additional commands, e-mail: general-help@... >> >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@... > For additional commands, e-mail: general-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by sebb-2-2
::
Rate this Message:
On 14 February 2012 17:08, Joe Schaefer <joe_schaefer@...> wrote:
> ----- Original Message ----- > >> From: Joe Schaefer <joe_schaefer@...> >> To: "general@..." <general@...> >> Cc: >> Sent: Tuesday, February 14, 2012 12:04 PM >> Subject: Re: migrating the main site to the CMS- a simple approach >> >>> ________________________________ >>> From: sebb <sebbaz@...> >>> To: general@... >>> Sent: Tuesday, February 14, 2012 11:57 AM >>> Subject: Re: migrating the main site to the CMS- a simple approach >>> >>> On 14 February 2012 16:21, Joe Schaefer <joe_schaefer@...> >> wrote: >>>> So I realize that I don't have enough time myself >>>> to convert the incubator site's content to markdown >>>> even tho there are scripts to automate that process. >>>> Instead let me offer a different idea- to keep the >>>> existing build system but superimpose the CMS on top >>>> of it. >>> >>>> To facilitate this, all that needs to happen is for >>>> someone to find a generic way of invoking anakia so >>>> it satisfies the command-line interface of >>>> >>>> https://svn.apache.org/repos/infra/websites/cms/build/build_external.pl >>>> >>>> (ie builds sources from ./content/ into a specified target >>>> dir). >>> >>> That's not actually sufficient to build the main Incubator site, >>> because it does not take the Clutch updates into account. >>> >>> However, I guess Clutch could be run separately to update the source >>> files, and then trigger a site rebuild. > > Alternately, if the clutch builds simply modify source content, Yes, that's all it does. > that aspect can be performed manually and the build system will > generate that content from the changes to the source content. > All someone would have to do in addition to what they already > already do now is publish the changes to the live site. However, the site build does a lot more than just run Anakia. It also runs XSLT and texen; each is run several times with different data. There are some other stages as well. This is all done by Ant, using the build.xml from the top-level directory. I suspect this is also true of a lot of other sites which use Anakia. >> >> >> Ideally the Clutch updates can be considered as "dynamic content" for >> the CMS, so we can simply schedule clutch builds on a periodic basis. >> That is done separately from the generic process of doing anakia builds. >> >> >>> >>>> By generic, I mean a suitable command-line invocation >>>> for the build_external.pl script for the "anakia" type >>>> (basically supplying the right @system_args in the script) >>>> so that pretty much any site currently using anakia will >>>> be able to do the same thing. >>>> >>>> Hopefully the challenge to produce such @system_args is >>>> within the means of this community ;-)- it amounts to >>>> 1 line of perl at this point. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: general-unsubscribe@... >>> For additional commands, e-mail: general-help@... >>> >>> >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscribe@... >> For additional commands, e-mail: general-help@... >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@... > For additional commands, e-mail: general-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by Joe Schaefer-6
::
Rate this Message:
----- Original Message -----
> From: sebb <sebbaz@...> > To: general@...; Joe Schaefer <joe_schaefer@...> > Cc: > Sent: Tuesday, February 14, 2012 1:04 PM > Subject: Re: migrating the main site to the CMS- a simple approach > > On 14 February 2012 17:08, Joe Schaefer <joe_schaefer@...> wrote: >> ----- Original Message ----- >> >>> From: Joe Schaefer <joe_schaefer@...> >>> To: "general@..." > <general@...> >>> Cc: >>> Sent: Tuesday, February 14, 2012 12:04 PM >>> Subject: Re: migrating the main site to the CMS- a simple approach >>> >>>> ________________________________ >>>> From: sebb <sebbaz@...> >>>> To: general@... >>>> Sent: Tuesday, February 14, 2012 11:57 AM >>>> Subject: Re: migrating the main site to the CMS- a simple approach >>>> >>>> On 14 February 2012 16:21, Joe Schaefer > <joe_schaefer@...> >>> wrote: >>>>> So I realize that I don't have enough time myself >>>>> to convert the incubator site's content to markdown >>>>> even tho there are scripts to automate that process. >>>>> Instead let me offer a different idea- to keep the >>>>> existing build system but superimpose the CMS on top >>>>> of it. >>>> >>>>> To facilitate this, all that needs to happen is for >>>>> someone to find a generic way of invoking anakia so >>>>> it satisfies the command-line interface of >>>>> >>>>> > https://svn.apache.org/repos/infra/websites/cms/build/build_external.pl >>>>> >>>>> (ie builds sources from ./content/ into a specified target >>>>> dir). >>>> >>>> That's not actually sufficient to build the main Incubator > site, >>>> because it does not take the Clutch updates into account. >>>> >>>> However, I guess Clutch could be run separately to update the > source >>>> files, and then trigger a site rebuild. >> >> Alternately, if the clutch builds simply modify source content, > > Yes, that's all it does. > >> that aspect can be performed manually and the build system will >> generate that content from the changes to the source content. >> All someone would have to do in addition to what they already >> already do now is publish the changes to the live site. > > However, the site build does a lot more than just run Anakia. > > It also runs XSLT and texen; each is run several times with different data. > There are some other stages as well. > > This is all done by Ant, using the build.xml from the top-level directory. > > I suspect this is also true of a lot of other sites which use Anakia. Well whatever- we can change the build type from anakia to ant. That's no big deal. All we need at this point for CMS support is: 1) to change the name of the directory holding the site sources to "content", 2) to figure out what command-line arguments to pass to ant or to build.sh or whatever to tell it to build to a specified target directory also named "content" but with a different base directory. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by sebb-2-2
::
Rate this Message:
On 14 February 2012 18:09, Joe Schaefer <joe_schaefer@...> wrote:
> ----- Original Message ----- > >> From: sebb <sebbaz@...> >> To: general@...; Joe Schaefer <joe_schaefer@...> >> Cc: >> Sent: Tuesday, February 14, 2012 1:04 PM >> Subject: Re: migrating the main site to the CMS- a simple approach >> >> On 14 February 2012 17:08, Joe Schaefer <joe_schaefer@...> wrote: >>> ----- Original Message ----- >>> >>>> From: Joe Schaefer <joe_schaefer@...> >>>> To: "general@..." >> <general@...> >>>> Cc: >>>> Sent: Tuesday, February 14, 2012 12:04 PM >>>> Subject: Re: migrating the main site to the CMS- a simple approach >>>> >>>>> ________________________________ >>>>> From: sebb <sebbaz@...> >>>>> To: general@... >>>>> Sent: Tuesday, February 14, 2012 11:57 AM >>>>> Subject: Re: migrating the main site to the CMS- a simple approach >>>>> >>>>> On 14 February 2012 16:21, Joe Schaefer >> <joe_schaefer@...> >>>> wrote: >>>>>> So I realize that I don't have enough time myself >>>>>> to convert the incubator site's content to markdown >>>>>> even tho there are scripts to automate that process. >>>>>> Instead let me offer a different idea- to keep the >>>>>> existing build system but superimpose the CMS on top >>>>>> of it. >>>>> >>>>>> To facilitate this, all that needs to happen is for >>>>>> someone to find a generic way of invoking anakia so >>>>>> it satisfies the command-line interface of >>>>>> >>>>>> >> https://svn.apache.org/repos/infra/websites/cms/build/build_external.pl >>>>>> >>>>>> (ie builds sources from ./content/ into a specified target >>>>>> dir). >>>>> >>>>> That's not actually sufficient to build the main Incubator >> site, >>>>> because it does not take the Clutch updates into account. >>>>> >>>>> However, I guess Clutch could be run separately to update the >> source >>>>> files, and then trigger a site rebuild. >>> >>> Alternately, if the clutch builds simply modify source content, >> >> Yes, that's all it does. >> >>> that aspect can be performed manually and the build system will >>> generate that content from the changes to the source content. >>> All someone would have to do in addition to what they already >>> already do now is publish the changes to the live site. >> >> However, the site build does a lot more than just run Anakia. >> >> It also runs XSLT and texen; each is run several times with different data. >> There are some other stages as well. >> >> This is all done by Ant, using the build.xml from the top-level directory. >> >> I suspect this is also true of a lot of other sites which use Anakia. > > Well whatever- we can change the build type from anakia to ant. That's > no big deal. All we need at this point for CMS support is: > > 1) to change the name of the directory holding the site sources to "content", The sources are held under: https://svn.apache.org/repos/asf/incubator/public/trunk/site-author However, there are support files in other directories, in particular the lib/ directory. > 2) to figure out what command-line arguments to pass to ant or to build.sh or > whatever to tell it to build to a specified target directory also named "content" > but with a different base directory. The output currently goes to https://svn.apache.org/repos/asf/incubator/public/trunk/site-publish. I think most files under site-publish are derived from site-author; however there are probably some that are only in site-publish. For example, .htaccess seems to be only in site-publish. Probably the first task is to ensure that all site-publish files are derivable from site-author. Can then rename the input directory, and fix up the build file. Changing the output directory would be a bit more involved as it is used for the workspace on minotaur. Would it be possible to switch to the eventual svnpubsub target without actually switching to CMS yet? Could then switch the workspace on minotaur to use the new content output directory. Once that's working, then CMS could be plugged in. > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@... > For additional commands, e-mail: general-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by Joe Schaefer-6
::
Rate this Message:
----- Original Message -----
> From: sebb <sebbaz@...> > To: general@...; Joe Schaefer <joe_schaefer@...> > Cc: > Sent: Tuesday, February 14, 2012 1:36 PM > Subject: Re: migrating the main site to the CMS- a simple approach > > On 14 February 2012 18:09, Joe Schaefer <joe_schaefer@...> wrote: >> ----- Original Message ----- >> >>> From: sebb <sebbaz@...> >>> To: general@...; Joe Schaefer > <joe_schaefer@...> >>> Cc: >>> Sent: Tuesday, February 14, 2012 1:04 PM >>> Subject: Re: migrating the main site to the CMS- a simple approach >>> >>> On 14 February 2012 17:08, Joe Schaefer <joe_schaefer@...> > wrote: >>>> ----- Original Message ----- >>>> >>>>> From: Joe Schaefer <joe_schaefer@...> >>>>> To: "general@..." >>> <general@...> >>>>> Cc: >>>>> Sent: Tuesday, February 14, 2012 12:04 PM >>>>> Subject: Re: migrating the main site to the CMS- a simple > approach >>>>> >>>>>> ________________________________ >>>>>> From: sebb <sebbaz@...> >>>>>> To: general@... >>>>>> Sent: Tuesday, February 14, 2012 11:57 AM >>>>>> Subject: Re: migrating the main site to the CMS- a simple > approach >>>>>> >>>>>> On 14 February 2012 16:21, Joe Schaefer >>> <joe_schaefer@...> >>>>> wrote: >>>>>>> So I realize that I don't have enough time myself >>>>>>> to convert the incubator site's content to > markdown >>>>>>> even tho there are scripts to automate that process. >>>>>>> Instead let me offer a different idea- to keep the >>>>>>> existing build system but superimpose the CMS on top >>>>>>> of it. >>>>>> >>>>>>> To facilitate this, all that needs to happen is for >>>>>>> someone to find a generic way of invoking anakia so >>>>>>> it satisfies the command-line interface of >>>>>>> >>>>>>> >>> > https://svn.apache.org/repos/infra/websites/cms/build/build_external.pl >>>>>>> >>>>>>> (ie builds sources from ./content/ into a specified > target >>>>>>> dir). >>>>>> >>>>>> That's not actually sufficient to build the main > Incubator >>> site, >>>>>> because it does not take the Clutch updates into account. >>>>>> >>>>>> However, I guess Clutch could be run separately to update > the >>> source >>>>>> files, and then trigger a site rebuild. >>>> >>>> Alternately, if the clutch builds simply modify source content, >>> >>> Yes, that's all it does. >>> >>>> that aspect can be performed manually and the build system will >>>> generate that content from the changes to the source content. >>>> All someone would have to do in addition to what they already >>>> already do now is publish the changes to the live site. >>> >>> However, the site build does a lot more than just run Anakia. >>> >>> It also runs XSLT and texen; each is run several times with different > data. >>> There are some other stages as well. >>> >>> This is all done by Ant, using the build.xml from the top-level > directory. >>> >>> I suspect this is also true of a lot of other sites which use Anakia. >> >> Well whatever- we can change the build type from anakia to ant. That's >> no big deal. All we need at this point for CMS support is: >> >> 1) to change the name of the directory holding the site sources to > "content", > > The sources are held under: > https://svn.apache.org/repos/asf/incubator/public/trunk/site-author So rename site-author to "content". That'd be step 1 precisely. > > However, there are support files in other directories, in particular > the lib/ directory. That has no material impact on what I'm proposing: just leave those where they are. > >> 2) to figure out what command-line arguments to pass to ant or to build.sh > or >> whatever to tell it to build to a specified target directory also named > "content" >> but with a different base directory. > > The output currently goes to > https://svn.apache.org/repos/asf/incubator/public/trunk/site-publish. > > I think most files under site-publish are derived from site-author; > however there are probably some that are only in site-publish. > For example, .htaccess seems to be only in site-publish. Well that would need to go into the "content" dir and ant would need to copy it over to the target "content" dir. > > Probably the first task is to ensure that all site-publish files are > derivable from site-author. Yes. > > Can then rename the input directory, and fix up the build file. > > Changing the output directory would be a bit more involved as it is > used for the workspace on minotaur. Well can't we make this configurable? I mean cmon it's 2012, surely we can pass some argument to build.sh that tells it to use a different directory other than site-publish. > Would it be possible to switch to the eventual svnpubsub target > without actually switching to CMS yet? > Could then switch the workspace on minotaur to use the new content > output directory. > > Once that's working, then CMS could be plugged in. I've outlined the approach I recommend- to rename the source dir, make everything that's in the output dir come from the build process (not necessarily the source dir), and to make the target dir a command-line option to build.sh / ant / whatever. That would entail no material changes to the workflow for this project other than editing stuff in content instead of site-author, and will allow migration to the CMS at any point down the road. If you prefer your approach, all you need to do is change the site-publish dir to an svn external pointing at the infra/websites/production/incubator/content dir in the infra repo. I think that will just confuse things more than it will help for the time being tho. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by Daniel Shahaf-2
::
Rate this Message:
Joe Schaefer wrote on Tue, Feb 14, 2012 at 10:47:19 -0800:
> If you prefer your approach, all you need to do is change the site-publish > dir to an svn external pointing at the infra/websites/production/incubator/content External within what? You can't checkout an external unless it's a child of something, but for svnpubsub you want precisely to checkout just site-publish without its parents. > dir in the infra repo. I think that will just confuse things more than > it will help for the time being tho. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@... > For additional commands, e-mail: general-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by Joe Schaefer-6
::
Rate this Message:
----- Original Message -----
> From: Daniel Shahaf <d.s@...> > To: Joe Schaefer <joe_schaefer@...> > Cc: sebb <sebbaz@...>; "general@..." <general@...> > Sent: Tuesday, February 14, 2012 4:21 PM > Subject: Re: migrating the main site to the CMS- a simple approach > > Joe Schaefer wrote on Tue, Feb 14, 2012 at 10:47:19 -0800: >> If you prefer your approach, all you need to do is change the site-publish >> dir to an svn external pointing at the > infra/websites/production/incubator/content > > External within what? You can't checkout an external unless it's Within trunk of course. > a child of something, but for svnpubsub you want precisely to checkout > just site-publish without its parents. Yes but for svnpubsub you'd use the infra repo directly, not the external. >> dir in the infra repo. I think that will just confuse things more than >> it will help for the time being tho. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscribe@... >> For additional commands, e-mail: general-help@... >> > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by Joe Schaefer-6
::
Rate this Message:
----- Original Message -----
> From: Joe Schaefer <joe_schaefer@...> > To: sebb <sebbaz@...>; "general@..." <general@...> > Cc: > Sent: Tuesday, February 14, 2012 1:47 PM > Subject: Re: migrating the main site to the CMS- a simple approach > > ----- Original Message ----- > >> From: sebb <sebbaz@...> >> To: general@...; Joe Schaefer > <joe_schaefer@...> >> Cc: >> Sent: Tuesday, February 14, 2012 1:36 PM >> Subject: Re: migrating the main site to the CMS- a simple approach >> >> On 14 February 2012 18:09, Joe Schaefer <joe_schaefer@...> > wrote: >>> ----- Original Message ----- >>> >>>> From: sebb <sebbaz@...> >>>> To: general@...; Joe Schaefer >> <joe_schaefer@...> >>>> Cc: >>>> Sent: Tuesday, February 14, 2012 1:04 PM >>>> Subject: Re: migrating the main site to the CMS- a simple approach >>>> >>>> On 14 February 2012 17:08, Joe Schaefer > <joe_schaefer@...> >> wrote: >>>>> ----- Original Message ----- >>>>> >>>>>> From: Joe Schaefer <joe_schaefer@...> >>>>>> To: "general@..." >>>> <general@...> >>>>>> Cc: >>>>>> Sent: Tuesday, February 14, 2012 12:04 PM >>>>>> Subject: Re: migrating the main site to the CMS- a simple > >> approach >>>>>> >>>>>>> ________________________________ >>>>>>> From: sebb <sebbaz@...> >>>>>>> To: general@... >>>>>>> Sent: Tuesday, February 14, 2012 11:57 AM >>>>>>> Subject: Re: migrating the main site to the CMS- a > simple >> approach >>>>>>> >>>>>>> On 14 February 2012 16:21, Joe Schaefer >>>> <joe_schaefer@...> >>>>>> wrote: >>>>>>>> So I realize that I don't have enough time > myself >>>>>>>> to convert the incubator site's content to >> markdown >>>>>>>> even tho there are scripts to automate that > process. >>>>>>>> Instead let me offer a different idea- to keep > the >>>>>>>> existing build system but superimpose the CMS on > top >>>>>>>> of it. >>>>>>> >>>>>>>> To facilitate this, all that needs to happen is > for >>>>>>>> someone to find a generic way of invoking anakia > so >>>>>>>> it satisfies the command-line interface of >>>>>>>> >>>>>>>> >>>> >> https://svn.apache.org/repos/infra/websites/cms/build/build_external.pl >>>>>>>> >>>>>>>> (ie builds sources from ./content/ into a > specified >> target >>>>>>>> dir). >>>>>>> >>>>>>> That's not actually sufficient to build the main >> Incubator >>>> site, >>>>>>> because it does not take the Clutch updates into > account. >>>>>>> >>>>>>> However, I guess Clutch could be run separately to > update >> the >>>> source >>>>>>> files, and then trigger a site rebuild. >>>>> >>>>> Alternately, if the clutch builds simply modify source > content, >>>> >>>> Yes, that's all it does. >>>> >>>>> that aspect can be performed manually and the build system > will >>>>> generate that content from the changes to the source content. >>>>> All someone would have to do in addition to what they already >>>>> already do now is publish the changes to the live site. >>>> >>>> However, the site build does a lot more than just run Anakia. >>>> >>>> It also runs XSLT and texen; each is run several times with > different >> data. >>>> There are some other stages as well. >>>> >>>> This is all done by Ant, using the build.xml from the top-level >> directory. >>>> >>>> I suspect this is also true of a lot of other sites which use > Anakia. >>> >>> Well whatever- we can change the build type from anakia to ant. > That's >>> no big deal. All we need at this point for CMS support is: >>> >>> 1) to change the name of the directory holding the site sources to >> "content", >> >> The sources are held under: >> https://svn.apache.org/repos/asf/incubator/public/trunk/site-author > > So rename site-author to "content". That'd be step 1 precisely. > >> >> However, there are support files in other directories, in particular >> the lib/ directory. > > That has no material impact on what I'm proposing: just leave those > where they are. > >> >>> 2) to figure out what command-line arguments to pass to ant or to > build.sh >> or >>> whatever to tell it to build to a specified target directory also > named >> "content" >>> but with a different base directory. >> >> The output currently goes to >> https://svn.apache.org/repos/asf/incubator/public/trunk/site-publish. >> >> I think most files under site-publish are derived from site-author; >> however there are probably some that are only in site-publish. >> For example, .htaccess seems to be only in site-publish. > > Well that would need to go into the "content" dir and ant would need > to copy it over to the target "content" dir. > >> >> Probably the first task is to ensure that all site-publish files are >> derivable from site-author. > > Yes. > >> >> Can then rename the input directory, and fix up the build file. >> >> Changing the output directory would be a bit more involved as it is >> used for the workspace on minotaur. > > Well can't we make this configurable? I mean cmon it's 2012, surely > we can pass some argument to build.sh that tells it to use a different > directory other than site-publish. > >> Would it be possible to switch to the eventual svnpubsub target >> without actually switching to CMS yet? >> Could then switch the workspace on minotaur to use the new content >> output directory. >> >> Once that's working, then CMS could be plugged in. > > I've outlined the approach I recommend- to rename the source dir, > make everything that's in the output dir come from the build process > (not necessarily the source dir), and to make the target dir a command-line > option to build.sh / ant / whatever. I committed build_cms.sh which implements the necessities. All we need to do is ferret thru the build output to ensure everything matches up with the source material. The simplest way to do this is to rm -rf the site-publish dir in your local checkout and then do an ant build (assuming you have svn 1.7 here) after recreating an empty site-publish dir. Then svn status will tell you which files are missing by indicating those lines with an "!" prefix. I hope that those missing files can simply be copied back to the site-author dir and that a subsequent build will fix the "missing" lines in svn status. I have a hunch this will be a nontrivial list given the number of times I've seen people commit stuff to the wrong tree, but maybe my pessimism of late is unwarranted here. I don't have a handy way of carrying this out, and while there's no particular rush to get this done soon I would appreciate it if someone could do the necessary work here. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by sebb-2-2
::
Rate this Message:
On 14 February 2012 22:47, Joe Schaefer <joe_schaefer@...> wrote:
> ----- Original Message ----- > >> From: Joe Schaefer <joe_schaefer@...> >> To: sebb <sebbaz@...>; "general@..." <general@...> >> Cc: >> Sent: Tuesday, February 14, 2012 1:47 PM >> Subject: Re: migrating the main site to the CMS- a simple approach >> >> ----- Original Message ----- >> >>> From: sebb <sebbaz@...> >>> To: general@...; Joe Schaefer >> <joe_schaefer@...> >>> Cc: >>> Sent: Tuesday, February 14, 2012 1:36 PM >>> Subject: Re: migrating the main site to the CMS- a simple approach >>> >>> On 14 February 2012 18:09, Joe Schaefer <joe_schaefer@...> >> wrote: >>>> ----- Original Message ----- >>>> >>>>> From: sebb <sebbaz@...> >>>>> To: general@...; Joe Schaefer >>> <joe_schaefer@...> >>>>> Cc: >>>>> Sent: Tuesday, February 14, 2012 1:04 PM >>>>> Subject: Re: migrating the main site to the CMS- a simple approach >>>>> >>>>> On 14 February 2012 17:08, Joe Schaefer >> <joe_schaefer@...> >>> wrote: >>>>>> ----- Original Message ----- >>>>>> >>>>>>> From: Joe Schaefer <joe_schaefer@...> >>>>>>> To: "general@..." >>>>> <general@...> >>>>>>> Cc: >>>>>>> Sent: Tuesday, February 14, 2012 12:04 PM >>>>>>> Subject: Re: migrating the main site to the CMS- a simple >> >>> approach >>>>>>> >>>>>>>> ________________________________ >>>>>>>> From: sebb <sebbaz@...> >>>>>>>> To: general@... >>>>>>>> Sent: Tuesday, February 14, 2012 11:57 AM >>>>>>>> Subject: Re: migrating the main site to the CMS- a >> simple >>> approach >>>>>>>> >>>>>>>> On 14 February 2012 16:21, Joe Schaefer >>>>> <joe_schaefer@...> >>>>>>> wrote: >>>>>>>>> So I realize that I don't have enough time >> myself >>>>>>>>> to convert the incubator site's content to >>> markdown >>>>>>>>> even tho there are scripts to automate that >> process. >>>>>>>>> Instead let me offer a different idea- to keep >> the >>>>>>>>> existing build system but superimpose the CMS on >> top >>>>>>>>> of it. >>>>>>>> >>>>>>>>> To facilitate this, all that needs to happen is >> for >>>>>>>>> someone to find a generic way of invoking anakia >> so >>>>>>>>> it satisfies the command-line interface of >>>>>>>>> >>>>>>>>> >>>>> >>> https://svn.apache.org/repos/infra/websites/cms/build/build_external.pl >>>>>>>>> >>>>>>>>> (ie builds sources from ./content/ into a >> specified >>> target >>>>>>>>> dir). >>>>>>>> >>>>>>>> That's not actually sufficient to build the main >>> Incubator >>>>> site, >>>>>>>> because it does not take the Clutch updates into >> account. >>>>>>>> >>>>>>>> However, I guess Clutch could be run separately to >> update >>> the >>>>> source >>>>>>>> files, and then trigger a site rebuild. >>>>>> >>>>>> Alternately, if the clutch builds simply modify source >> content, >>>>> >>>>> Yes, that's all it does. >>>>> >>>>>> that aspect can be performed manually and the build system >> will >>>>>> generate that content from the changes to the source content. >>>>>> All someone would have to do in addition to what they already >>>>>> already do now is publish the changes to the live site. >>>>> >>>>> However, the site build does a lot more than just run Anakia. >>>>> >>>>> It also runs XSLT and texen; each is run several times with >> different >>> data. >>>>> There are some other stages as well. >>>>> >>>>> This is all done by Ant, using the build.xml from the top-level >>> directory. >>>>> >>>>> I suspect this is also true of a lot of other sites which use >> Anakia. >>>> >>>> Well whatever- we can change the build type from anakia to ant. >> That's >>>> no big deal. All we need at this point for CMS support is: >>>> >>>> 1) to change the name of the directory holding the site sources to >>> "content", >>> >>> The sources are held under: >>> https://svn.apache.org/repos/asf/incubator/public/trunk/site-author >> >> So rename site-author to "content". That'd be step 1 precisely. >> >>> >>> However, there are support files in other directories, in particular >>> the lib/ directory. >> >> That has no material impact on what I'm proposing: just leave those >> where they are. >> >>> >>>> 2) to figure out what command-line arguments to pass to ant or to >> build.sh >>> or >>>> whatever to tell it to build to a specified target directory also >> named >>> "content" >>>> but with a different base directory. >>> >>> The output currently goes to >>> https://svn.apache.org/repos/asf/incubator/public/trunk/site-publish. >>> >>> I think most files under site-publish are derived from site-author; >>> however there are probably some that are only in site-publish. >>> For example, .htaccess seems to be only in site-publish. >> >> Well that would need to go into the "content" dir and ant would need >> to copy it over to the target "content" dir. >> >>> >>> Probably the first task is to ensure that all site-publish files are >>> derivable from site-author. >> >> Yes. >> >>> >>> Can then rename the input directory, and fix up the build file. >>> >>> Changing the output directory would be a bit more involved as it is >>> used for the workspace on minotaur. >> >> Well can't we make this configurable? I mean cmon it's 2012, surely >> we can pass some argument to build.sh that tells it to use a different >> directory other than site-publish. >> >>> Would it be possible to switch to the eventual svnpubsub target >>> without actually switching to CMS yet? >>> Could then switch the workspace on minotaur to use the new content >>> output directory. >>> >>> Once that's working, then CMS could be plugged in. >> >> I've outlined the approach I recommend- to rename the source dir, >> make everything that's in the output dir come from the build process >> (not necessarily the source dir), and to make the target dir a command-line >> option to build.sh / ant / whatever. > > I committed build_cms.sh which implements the necessities. All we > need to do is ferret thru the build output to ensure everything > matches up with the source material. The simplest way to do this > is to rm -rf the site-publish dir in your local checkout and then > do an ant build (assuming you have svn 1.7 here) after recreating > an empty site-publish dir. Then svn status will tell you which > files are missing by indicating those lines with an "!" prefix. > I hope that those missing files can simply be copied back to > the site-author dir and that a subsequent build will fix the > "missing" lines in svn status. I have a hunch this will be a > nontrivial list given the number of times I've seen people commit > stuff to the wrong tree, but maybe my pessimism of late is unwarranted > here. > > I don't have a handy way of carrying this out, and while there's no > particular rush to get this done soon I would appreciate it if someone > could do the necessary work here. I've made a start on it, but don't have time to complete it for a few days, probably Monday at the earliest. The first thing to do is to decide if the following directory tree can be junked: site-publish/projects/altrmi/ I suspect it can, as altrmi has moved elsewhere, but I just want to check it's not being kept for historical reasons. The other files currently only in site-publish are: ! 1243649 site-publish\projects\geronimo\status.html ! 1243649 site-publish\projects\geronimo\status.pdf ! 1243649 site-publish\projects\lcf.html ! 1243649 site-publish\projects\geronimo-proposal.html ! 1243649 site-publish\projects\ruper.html Again I'm not sure if these files are required or can be deleted. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by Joe Schaefer-6
::
Rate this Message:
----- Original Message -----
> From: sebb <sebbaz@...> > To: Joe Schaefer <joe_schaefer@...> > Cc: "general@..." <general@...> > Sent: Tuesday, February 14, 2012 7:59 PM > Subject: Re: migrating the main site to the CMS- a simple approach > > On 14 February 2012 22:47, Joe Schaefer <joe_schaefer@...> wrote: >> I committed build_cms.sh which implements the necessities. All we >> need to do is ferret thru the build output to ensure everything >> matches up with the source material. The simplest way to do this >> is to rm -rf the site-publish dir in your local checkout and then >> do an ant build (assuming you have svn 1.7 here) after recreating >> an empty site-publish dir. Then svn status will tell you which >> files are missing by indicating those lines with an "!" prefix. >> I hope that those missing files can simply be copied back to >> the site-author dir and that a subsequent build will fix the >> "missing" lines in svn status. I have a hunch this will be a >> nontrivial list given the number of times I've seen people commit >> stuff to the wrong tree, but maybe my pessimism of late is unwarranted >> here. >> >> I don't have a handy way of carrying this out, and while there's no >> particular rush to get this done soon I would appreciate it if someone >> could do the necessary work here. > > I've made a start on it, but don't have time to complete it for a few > days, probably Monday at the earliest. > > The first thing to do is to decide if the following directory tree can > be junked: > > site-publish/projects/altrmi/ > > I suspect it can, as altrmi has moved elsewhere, but I just want to > check it's not being kept for historical reasons. > > The other files currently only in site-publish are: > > ! 1243649 site-publish\projects\geronimo\status.html > ! 1243649 site-publish\projects\geronimo\status.pdf > ! 1243649 site-publish\projects\lcf.html > ! 1243649 site-publish\projects\geronimo-proposal.html > ! 1243649 site-publish\projects\ruper.html > > Again I'm not sure if these files are required or can be deleted. Thanks sebb! Again this work is all gating on infra updating the cms server to running FreeBSD 9 with fresh ports, which we are currently having some issues with. Optimistically this should happen within the next 30 days tho, but it's certainly good to see the early initiative! --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by Jukka Zitting
::
Rate this Message:
Hi,
On Wed, Feb 15, 2012 at 1:59 AM, sebb <sebbaz@...> wrote: > The first thing to do is to decide if the following directory tree can > be junked: > > site-publish/projects/altrmi/ > > I suspect it can, as altrmi has moved elsewhere, but I just want to > check it's not being kept for historical reasons. +1 to removing. We still have the content archived in svn history. > The other files currently only in site-publish are: > > ! 1243649 site-publish\projects\geronimo\status.html > ! 1243649 site-publish\projects\geronimo\status.pdf Remove. Geronimo status is at /projects/geronimo.html. > ! 1243649 site-publish\projects\lcf.html Remove. LCF renamed itself to ManifoldCF, and its status is now at /projects/manifoldcf.html. > ! 1243649 site-publish\projects\geronimo-proposal.html Keep. It should be linked to from the proposal list on the Incubator wiki, or perhaps migrated entirely into the wiki (or at least to a better place in site-author). > ! 1243649 site-publish\projects\ruper.html Remove. AFAICT, Ruper renamed itself to Depot, and its status is now at /projects/depot.html. BR, Jukka Zitting --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by sebb-2-2
::
Rate this Message:
On 15 February 2012 15:44, Jukka Zitting <jukka.zitting@...> wrote:
> Hi, > > On Wed, Feb 15, 2012 at 1:59 AM, sebb <sebbaz@...> wrote: >> The first thing to do is to decide if the following directory tree can >> be junked: >> >> site-publish/projects/altrmi/ >> >> I suspect it can, as altrmi has moved elsewhere, but I just want to >> check it's not being kept for historical reasons. > > +1 to removing. We still have the content archived in svn history. Done >> The other files currently only in site-publish are: >> >> ! 1243649 site-publish\projects\geronimo\status.html >> ! 1243649 site-publish\projects\geronimo\status.pdf > > Remove. Geronimo status is at /projects/geronimo.html. Done >> ! 1243649 site-publish\projects\lcf.html > > Remove. LCF renamed itself to ManifoldCF, and its status is now at > /projects/manifoldcf.html. Done >> ! 1243649 site-publish\projects\geronimo-proposal.html > > Keep. It should be linked to from the proposal list on the Incubator > wiki, or perhaps migrated entirely into the wiki (or at least to a > better place in site-author). Not sure why that file was flagged as a problem by my testing - there is a source file for it under site-author. >> ! 1243649 site-publish\projects\ruper.html > > Remove. AFAICT, Ruper renamed itself to Depot, and its status is now > at /projects/depot.html. Done. > BR, > > Jukka Zitting > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@... > For additional commands, e-mail: general-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
|
|
Re: migrating the main site to the CMS- a simple approach
by sebb-2-2
::
Rate this Message:
On 21 February 2012 02:31, sebb <sebbaz@...> wrote:
> On 15 February 2012 15:44, Jukka Zitting <jukka.zitting@...> wrote: >> Hi, >> >> On Wed, Feb 15, 2012 at 1:59 AM, sebb <sebbaz@...> wrote: >>> The first thing to do is to decide if the following directory tree can >>> be junked: >>> >>> site-publish/projects/altrmi/ >>> >>> I suspect it can, as altrmi has moved elsewhere, but I just want to >>> check it's not being kept for historical reasons. >> >> +1 to removing. We still have the content archived in svn history. > > Done > >>> The other files currently only in site-publish are: >>> >>> ! 1243649 site-publish\projects\geronimo\status.html >>> ! 1243649 site-publish\projects\geronimo\status.pdf >> >> Remove. Geronimo status is at /projects/geronimo.html. > > Done > >>> ! 1243649 site-publish\projects\lcf.html >> >> Remove. LCF renamed itself to ManifoldCF, and its status is now at >> /projects/manifoldcf.html. > > Done > >>> ! 1243649 site-publish\projects\geronimo-proposal.html >> >> Keep. It should be linked to from the proposal list on the Incubator >> wiki, or perhaps migrated entirely into the wiki (or at least to a >> better place in site-author). > > Not sure why that file was flagged as a problem by my testing - there > is a source file for it under site-author. Discovered the problem. There are two such html files, but only one source: site-author\projects\geronimo\geronimo-proposal.xml site-publish\projects\geronimo-proposal.html site-publish\projects\geronimo\geronimo-proposal.html It looks like the middle file was created a long time ago, and then the xml file was moved. So I will delete the middle file. >>> ! 1243649 site-publish\projects\ruper.html >> >> Remove. AFAICT, Ruper renamed itself to Depot, and its status is now >> at /projects/depot.html. > > Done. > >> BR, >> >> Jukka Zitting >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscribe@... >> For additional commands, e-mail: general-help@... >> --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@... For additional commands, e-mail: general-help@... |
| Free embeddable forum powered by Nabble | Forum Help |
