Re: migrate OSQA to static
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 ;)
Re: migrate OSQA to static
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
Re: migrate OSQA to static
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.
Re: migrate OSQA to static
Hi folks, Am 28.01.2019 um 14:08 schrieb cgrzemba--- via maintainers : > 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! :) >> >> --Maciej > > I made some improvements and replaced the OSQA URL with the static content. Thanks a lot for pushing this! At the moment I don’t have my head free for this, if you feel like it please go ahead with replacing Wordpress. Personally I refer this a lot: https://www.opencsw.org/extend-it/signup/to-upstream-maintainers/ and the filesearch and the package list. Best regards — Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896
Re: migrate OSQA to static
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! :) > > --Maciej > I made some improvements and replaced the OSQA URL with the static content. Carsten
Re: migrate OSQA to static
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! :) --Maciej
