From cgrzemba at opencsw.org Mon May 13 14:40:25 2019 From: cgrzemba at opencsw.org (cgrzemba at opencsw.org) Date: Mon, 13 May 2019 14:40:25 +0200 Subject: migrate OSQA to static In-Reply-To: <20190125154425.GA12124@google.com> References: <20190125154425.GA12124@google.com> Message-ID: On 25.01.19 16:44, Maciej Blizi?ski wrote: > > On Fri, Jan 25, 2019 at 03:05:33PM +0100, cgrzemba--- via maintainers wrote: > > I completed the work from weekend started in Dublin and the results are here for review: > > > > http://buildfarm.opencsw.org/~cgrzemba/osqa-static/ > > > > If there are no other concerns I would replace the Django OSQA with this static pages. > > Well done! It will be good riddance. > > The content is there, and URLs look the same (I didn't check all of them but > they look close enough). So I'd shut down the server-side execution as quickly > as possible. Then maybe do some more updates in the generated HTML files. > > I'd put everything in the code repo: the source data, the scripts, and the > generated HTML. > > Next up: get rid of Wordpress! :) > I am not sure if we should replace wp completely. There some pages which generated from dynamic content, like package list. So we should first define which content we want keep and which get rid of. The alternative, we could easy update to WP version 5.2. but I have no experiance if it has an impact of performance. -------------- next part -------------- An HTML attachment was scrubbed... URL: From maciej at opencsw.org Mon May 13 14:55:30 2019 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=) Date: Mon, 13 May 2019 13:55:30 +0100 Subject: migrate OSQA to static In-Reply-To: References: <20190125154425.GA12124@google.com> Message-ID: cgrzemba--- via maintainers escreveu no dia segunda, 13/05/2019 ?(s) 13:40: > I am not sure if we should replace wp completely. There some pages which > generated from dynamic content, like package list. So we should first > define which content we want keep and which get rid of. > Please correct me if I'm wrong; this is what I remember about the Wordpress bits: Those parts of code are not that related to Wordpress. They are pieces of code written by us (OpenCSW) and that access tables that are made by us. Wordpress serves us only as a framework, a glue between our custom code and the HTTP server. We could relatively easily run the custom pieces of code without Wordpress. It would require adapting the code, but we would not need to rewrite everything. Carsten, if you are spending any time on this, perhaps you could inventory the custom pages? Basically, what are the URLs and code locations. Then we could see what to do; continue with Wordpress or migrate to a more lightweight PHP framework. We could also run PHP from cron (daily?) to generate static HTTP pages, depending how many generated pages there are. Maciej -------------- next part -------------- An HTML attachment was scrubbed... URL: From cgrzemba at opencsw.org Mon May 13 15:14:36 2019 From: cgrzemba at opencsw.org (cgrzemba at opencsw.org) Date: Mon, 13 May 2019 15:14:36 +0200 Subject: migrate OSQA to static In-Reply-To: References: <20190125154425.GA12124@google.com> Message-ID: On 13.05.19 14:56, Maciej (Matchek) Blizi?ski wrote: > > > > cgrzemba--- via maintainers escreveu no dia segunda, 13/05/2019 ?(s) 13:40: > > > > I am not sure if we should replace wp completely. There some pages which generated from dynamic content, like package list. So we should first define which content we want keep and which get rid of. > > > > > Please correct me if I'm wrong; this is what I remember about the Wordpress bits: > > Those parts of code are not that related to Wordpress. They are pieces of code written by us (OpenCSW) and that access tables that are made by us. Wordpress serves us only as a framework, a glue between our custom code and the HTTP server. We could relatively easily run the custom pieces of code without Wordpress. It would require adapting the code, but we would not need to rewrite everything. > > it is PHP. What I saw is a wp-plugin written by William. Besides it would be nice to keep the style/theme but I have no idea how to replace the WP engine with static pages simply. > > > > > > > Carsten, if you are spending any time on this, perhaps you could inventory the custom pages? Basically, what are the URLs and code locations. Then we could see what to do; continue with Wordpress or migrate to a more lightweight PHP framework. > > We could also run PHP from cron (daily?) to generate static HTTP pages, depending how many generated pages there are. > > Maciej > > I'm honest, PHP is not my favorite ;) -------------- next part -------------- An HTML attachment was scrubbed... URL: From maciej at opencsw.org Thu May 16 21:50:27 2019 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_=28Matchek=29_Blizi=C5=84ski?=) Date: Thu, 16 May 2019 20:50:27 +0100 Subject: migrate OSQA to static In-Reply-To: References: <20190125154425.GA12124@google.com> Message-ID: cgrzemba at opencsw.org escreveu no dia segunda, 13/05/2019 ?(s) 14:14: > it is PHP. What I saw is a wp-plugin written by William. > Besides it would be nice to keep the style/theme but I have no idea how to > replace the WP engine with static pages simply. > Why would the style stop you from making the code better for us? In our list of priorities, the way things look is one of the last places. This might confirm the stereotype of "this looks horrible, it must have been designed by engineers", but who cares? What we want, is our website not being broken into. > We could also run PHP from cron (daily?) to generate static HTTP pages, > depending how many generated pages there are. > > I'm honest, PHP is not my favorite ;) Whatever you decide, is fine! --Maciej -------------- next part -------------- An HTML attachment was scrubbed... URL: