On Thu, Dec 27, 2012 at 10:34 AM, Glen Mazza <[email protected]> wrote:
> OK, answer to your first question is that the script expects a cgi-bin > folder, even if it's empty, so I just created one and SVN committed, > problem goes away then. > > Answer to your second question: Because neither you nor I can get the CSS > to appear and I don't understand why it's not popping up when I'm viewing > it from the browser (AFAIK those "absolute paths" should concatenated with > HTML base URL, allowing the CSS to get read in) That's not right. The concatenation is done only for relative paths. If we need to do local builds and load local files, then we should use relative paths instead. > I'm reluctant to have them switch over our website to Apache CMS without > first confirming it will look right when hosted. I asked them, in my last > comment ( > https://issues.apache.org/**jira/browse/INFRA-5631<https://issues.apache.org/jira/browse/INFRA-5631>), > to host it on roller2.apache.org so we can first confirm the CSS & logos > are being picked up, then move it to roller.apache.org. But I haven't > gotten a response from them since then, which I'm taking as implicit > permission we can continue with our presenting hosting method... :) > Personally, I'm fine with getting the site up in an ugly state and then tweaking it to make it look nice. Our current site is already pretty bare-bones ugly :-) > Answer to your third question: I think they call it "bookmarklet" and I > used it once when they told me to update the build instructions you were > following ( https://issues.apache.org/**jira/browse/INFRA-5378?** > focusedCommentId=13483183&**page=com.atlassian.jira.** > plugin.system.issuetabpanels:**comment-tabpanel#comment-**13483183<https://issues.apache.org/jira/browse/INFRA-5378?focusedCommentId=13483183&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13483183>). > It's located here for the Apache CMS: https://cms.apache.org/www/; You're > welcome to log in right now with your Apache ID and make changes to the CMS > documentation. > > That all said, I'm not sure we really need to switch to the Apache CMS, > I'm inclined to ask them for confirmation on that. For one thing, we don't > need the Wiki-like aspects of the Apache CMS, because we already got > Confluence, which they don't care about (as they stated in INFRA-5631) > given our simple non-separate-publishing implementation of it. Also, we do > not request any auto-publication on people.apache.org/roller, we manually > go in and do svn update ourselves for the refreshing. Providing Infra > doesn't care about us switching or not, I'm 50/50 on switching, either way > is fine for me. > >> My understanding is that we MUST either use the new CMS or svnpubsub. The CMS is built "on top" of svnpubsub. Maybe the CMS is overkill for our needs and svnpubsub would be fine for our single page homepage, and then we provide all other content via Confluence. - Dave > I'm getting raw text with no styling or images, but I assumed that was due >> to the absolute paths (e.g. /images/roller-logo.jpg) in the HTML. I do see >> the CSS files were generated and placed in content/css. >> >> - Dave >> >> >> >> On Thu, Dec 27, 2012 at 9:19 AM, Glen Mazza <[email protected]> wrote: >> >> Hi Dave, while I'm assembing answers to your questions (give me a few >>> minutes), quick question: were the stylesheets absorbed into the output >>> in >>> roller_cms_test, i.e., does it look stylistically like this: >>> http://incubator.apache.org/****jspwiki/<http://incubator.apache.org/**jspwiki/> >>> <http://incubator.**apache.org/jspwiki/<http://incubator.apache.org/jspwiki/>> >>> when you bring it up locally from a browser or are you just getting raw >>> >>> text with no CSS styling? (I got the latter, which concerns me because >>> IIRC I *was* able to get the CSS to appear when I generated JSPWiki >>> locally.) If you're getting the CSS in that's fantastic. >>> >>> Be right back with your questions... >>> >>> Glen >>> >>> >>> >>> On 12/27/2012 09:08 AM, Dave wrote: >>> >>> OK, I'm able to build the site locally based on the instructions. I get >>>> what could be considered an error message, but content is generated and >>>> it >>>> looks (on first glance) to be correct. >>>> >>>> apache_cms_build dave$ perl build_site.pl --source-base >>>> ../roller_cms/ >>>> --target-base /tmp/roller_cms_test >>>> Building site... >>>> Can't open cgi-bin [skipping]: No such file or directory at >>>> build_site.pl line 124. >>>> All done. >>>> >>>> A couple of questions, if you please: >>>> >>>> Should I be concerned about that "Can't open" message? >>>> >>>> What remains to be done to get our site up and running and how can I >>>> help? >>>> >>>> Once we get setup, will we ever need to do "local builds" again or will >>>> we >>>> be able to do everything through the web based tools? i.e. >>>> http://s.apache.org/cms-****tutorial<http://s.apache.org/cms-**tutorial>< >>>> http://s.apache.org/cms-**tutorial <http://s.apache.org/cms-tutorial>>. >>>> >>>> >>>> Thanks, >>>> - Dave >>>> >>>> >>>> >>>> >>>> On Wed, Dec 26, 2012 at 1:21 PM, David Johnson <[email protected]> >>>> wrote: >>>> >>>> On Dec 26, 2012, at 12:38 PM, Glen Mazza <[email protected]> wrote: >>>>> >>>>> I'm not sure why you needed to compile C source code (maybe something >>>>> specific with your OS)--I didn't have to, at least not with Ubuntu >>>>> Linux. >>>>> >>>> Remember, as the instructions stress there's *two* folders you have >>>> to >>>> deal with -- one where the CMS scripts are ("the build script >>>> directory") >>>> and other where the Roller CMS site is (trunk/cmssite off of >>>> subversion). >>>> That command you're having trouble with below needs to be run from the >>>> *former*, and it should have these files within it: >>>> >>>> gmazza@gmazza-work:/media/****work1/opensource/cms$ ls >>>>> >>>>> build_external.pl build_file.pl build_site.pl build_svn.pl lib >>>>>> >>>>>> markdownd.py mdx_elementid.py mdx_elementid.pyc >>>>> The last sentence of the first paragraph here: >>>>> http://apache.org/dev/cmsref.****html#local-build<http://apache.org/dev/cmsref.**html#local-build> >>>>> <http://**apache.org/dev/cmsref.html#**local-build<http://apache.org/dev/cmsref.html#local-build>>tells >>>>> you where to get the >>>>> >>>> build scripts, and it indeed does have markdownd.py there. >>>> >>>> Thanks for that tip. I'll give it another shot later today I hope. >>>>> >>>>> - Dave >>>>> >>>>> >>>>> >>>>> On 12/26/2012 12:21 PM, Dave wrote: >>>>> >>>>>> Thanks for getting this setup! >>>>>>> >>>>>>> I'm trying to follow those instructions and after a couple hour >>>>>>> >>>>>>> nightmare >>>>>> >>>>> of downloading Python and Perl dependencies, and compiling stuff from C >>>>> >>>>>> source code I get stuck at this point: >>>>>>> >>>>>>> Once everything is installed, navigate to the root folder of your CMS >>>>>>> >>>>>>> site >>>>>> >>>>> and run the following command: >>>>> >>>>>> $ export MARKDOWN_SOCKET=`pwd`/****markdown.socket PYTHONPATH=`pwd` >>>>>>> >>>>>>> >>>>>>> Next, navigate back to the build script directory (preferably in the >>>>>>> >>>>>>> same >>>>>> >>>>> command window, as the above environment variables must be set) and >>>>> >>>>>> run: >>>>>> >>>>> $ python markdownd.py >>>>> >>>>>> >>>>>>> roller_cms dave$ python markdownd.py >>>>>>> python: can't open file 'markdownd.py': [Errno 2] No such file >>>>>>> or >>>>>>> directory >>>>>>> >>>>>>> This is somewhat mysterious as the "sudo easy_install Markdown" >>>>>>> command >>>>>>> finished successfully. Any idea what I am doing wrong? >>>>>>> >>>>>>> - Dave >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Sat, Dec 15, 2012 at 8:45 PM, Glen Mazza <[email protected]> >>>>>>> >>>>>>> wrote: >>>>>> >>>>> Hi Team, I was working this evening on creating an Apache CMS version >>>>> >>>>>> of >>>>>>> >>>>>> the Roller website (quite thankfully, most of Roller is on the >>>>> >>>>>> Confluence >>>>>>> >>>>>> Wiki and that doesn't need conversion): https://issues.apache.org/** >>>>> >>>>>> jira/browse/INFRA-5631 < >>>>>>>> >>>>>>>> >>>>>>>> https://issues.apache.org/****jira/browse/INFRA-5631<https://issues.apache.org/**jira/browse/INFRA-5631> >>>>>>> <https:/**/issues.apache.org/jira/**browse/INFRA-5631<https://issues.apache.org/jira/browse/INFRA-5631> >>>>>>> >>. >>>>>>> >>>>>> This was in response to >>>> an email sent to the CXF PMC* listing our project >>>> >>>> among a few dozen needing an upgrade. >>>>> >>>>>> To create the site, I did exactly what the incubating Apache JSPWiki >>>>>>>> >>>>>>>> does: >>>>>>> >>>>>> http://incubator.apache.org/******jspwiki/development/edit_******<http://incubator.apache.org/****jspwiki/development/edit_****> >>>>> >>>>>> website.html<http://incubator.**apache.org/**jspwiki/** >>>>>>>> development/edit_**website.**html<http://incubator.apache.org/**jspwiki/development/edit_**website.html> >>>>>>>> > >>>>>>>> < >>>>>>>> >>>>>>>> http://incubator.apache.org/****jspwiki/development/edit_**** >>>>>>> website.html<http://incubator.apache.org/**jspwiki/development/edit_**website.html> >>>>>>> <http://incubator.**apache.org/jspwiki/** >>>>>>> development/edit_website.html<http://incubator.apache.org/jspwiki/development/edit_website.html> >>>>>>> >**>. >>>>>>> >>>>>> Note >>>> the instructions on that page, as well as the instructions that it >>>> >>>> links to on building the CMS site locally before committing ( >>>>> >>>>>> http://apache.org/dev/cmsref.******html#local-build<http://apache.org/dev/cmsref.****html#local-build> >>>>>>>> <http://**apache.org/dev/cmsref.**html#**local-build<http://apache.org/dev/cmsref.**html#local-build> >>>>>>>> > >>>>>>>> < >>>>>>>> >>>>>>>> >>>>>>>> http://apache.org/dev/cmsref.****html#local-build<http://apache.org/dev/cmsref.**html#local-build> >>>>>>> <http://**apache.org/dev/cmsref.html#**local-build<http://apache.org/dev/cmsref.html#local-build> >>>>>>> > >>>>>>> >>>>>> ) >>>>> were updated earlier by me and I tried to make the instructions as >>>>> >>>>>> clear as >>>>>>> >>>>>> possible. >>>>> >>>>>> It would be good if others besides me tried to build the "cmssite" on >>>>>>>> their local machine ( >>>>>>>> https://svn.apache.org/repos/******<https://svn.apache.org/repos/****> >>>>>>>> <https://svn.apache.org/**repos/**<https://svn.apache.org/repos/**> >>>>>>>> > >>>>>>>> asf/roller/trunk/cmssite/< >>>>>>>> >>>>>>>> >>>>>>>> https://svn.apache.org/repos/****asf/roller/trunk/cmssite/<https://svn.apache.org/repos/**asf/roller/trunk/cmssite/> >>>>>>> <htt**ps://svn.apache.org/repos/asf/**roller/trunk/cmssite/<https://svn.apache.org/repos/asf/roller/trunk/cmssite/> >>>>>>> > >>>>>>> >>>>>> ) >>>>> using the instructions above, just so you know how to do it. Once >>>>> >>>>>> this is >>>>>>> >>>>>> in place, I suspect this will be a rare process as the Apache CMS >>>>> >>>>>> allows >>>>>>> >>>>>> you to make updates on-the-page for those with committer rights, quite >>>>> >>>>>> similar to Confluence. The problem with building locally, however, >>>>>>>> >>>>>>>> is that >>>>>>> >>>>>> for some reason the stylesheets do not get activated (even building >>>>> >>>>>> Apache >>>>>>> >>>>>> JSPWiki locally I encountered the same problem, although I thought I >>>>> >>>>>> had it >>>>>>> >>>>>> working before with them...), even though they are available and being >>>>> >>>>>> called seemingly properly by the HTMLs. I think my next step is to >>>>>>>> >>>>>>>> see if >>>>>>> >>>>>> Infra can create a staging (non-production) area or a temporary >>>>> >>>>>> roller2.apache.org for me to test that the stylesheets are getting >>>>>>>> activated if hosted on a web server. Once this process is working, >>>>>>>> >>>>>>>> then we >>>>>>> >>>>>> can switch the Apache CMS version to roller.apache.org. Thoughts, >>>>> >>>>>> comments welcome. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Glen >>>>>>>> >>>>>>>> >
