Hey everyone,
Well, it’s lasted 15 years, but my old website has run out of gas. Specifically, it was created using Python 2, and that’s going to be unsupported at the end of 2019, so time to re-write in Python 3.
Gone are Apache and mod_wsgi; it’s now running on nginx and uwsgi. The hardest part was choosing a CSS framework, and I tried a lot of them before settling on Materialize (https://materializecss.com/). It’s light, easy to use, and responsive.
Under the hood I’ve replaced how archived email messages are stored and processed. Before it was MariaDB using its fulltext index; now everything is stored in Elasticsearch, where full text searching is native. I’ve run a lot of tests, and queries take about 1/10 the time as before.
Of course, there may be glitches, and I’d like to know about them if you find them. I’ve also tried to keep the URLs the same, but some are not. One example is the archive search:
Before: https://leafe.com/archives/search/<listname> After: https://leafe.com/archives
My old web framework (Pylons) made it difficult to combine the lists into a single form, but the new framework (Flask) makes things much simpler. I’ve added a redirect for some of the old URLs, but not all, so if there are any that are causing you pain, let me know.
The new site should be available as soon as the DNS update propagates through the inter webs.
-- Ed Leafe
Hi
I love the new website but have come across an issue: Searching for ODBC as the search term, "All Messages" gives "502 Bad Gateway"
Paul Newton
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Ed Leafe Sent: 28 April 2019 18:32 To: profoxtech@leafe.com Subject: [ADMIN] Updated Website
Sent by an external sender ------------------------------
Hey everyone,
Well, it’s lasted 15 years, but my old website has run out of gas. Specifically, it was created using Python 2, and that’s going to be unsupported at the end of 2019, so time to re-write in Python 3.
Gone are Apache and mod_wsgi; it’s now running on nginx and uwsgi. The hardest part was choosing a CSS framework, and I tried a lot of them before settling on Materialize (https://materializecss.com/). It’s light, easy to use, and responsive.
Under the hood I’ve replaced how archived email messages are stored and processed. Before it was MariaDB using its fulltext index; now everything is stored in Elasticsearch, where full text searching is native. I’ve run a lot of tests, and queries take about 1/10 the time as before.
Of course, there may be glitches, and I’d like to know about them if you find them. I’ve also tried to keep the URLs the same, but some are not. One example is the archive search:
Before: https://leafe.com/archives/search/<listname> After: https://leafe.com/archives
My old web framework (Pylons) made it difficult to combine the lists into a single form, but the new framework (Flask) makes things much simpler. I’ve added a redirect for some of the old URLs, but not all, so if there are any that are causing you pain, let me know.
The new site should be available as soon as the DNS update propagates through the inter webs.
-- Ed Leafe
_______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/D9C79F5C-535D-4B30-A208-1B2A2023BA12@... ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious. Report [OT] Abuse: http://leafe.com/reportAbuse/D9C79F5C-535D-4B30-A208-1B2A2023BA12@leafe.com
On Apr 29, 2019, at 2:24 AM, Paul Newton Paul.Newton@pegasus.co.uk wrote:
I love the new website but have come across an issue: Searching for ODBC as the search term, "All Messages" gives "502 Bad Gateway"
I looked through the logs, and it appears that Flask uses cookie-based sessions by default. Since the session stores all the matching message numbers for paging, those cookies can get BIG, and surpass the 4K limit. Your query returned almost 5000 matches!
To fix that I need to make some changes to support server-side sessions. In the meantime, try searching a narrower range. :)
-- Ed Leafe
Thanks Ed
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Ed Leafe Sent: 29 April 2019 14:32 To: profoxtech@leafe.com Subject: Re: [ADMIN] Updated Website
Sent by an external sender ------------------------------
On Apr 29, 2019, at 2:24 AM, Paul Newton Paul.Newton@pegasus.co.uk wrote:
I love the new website but have come across an issue: Searching for ODBC as the search term, "All Messages" gives "502 Bad Gateway"
I looked through the logs, and it appears that Flask uses cookie-based sessions by default. Since the session stores all the matching message numbers for paging, those cookies can get BIG, and surpass the 4K limit. Your query returned almost 5000 matches!
To fix that I need to make some changes to support server-side sessions. In the meantime, try searching a narrower range. :)
-- Ed Leafe
[excessive quoting removed by server]
On Apr 29, 2019, at 2:24 AM, Paul Newton Paul.Newton@pegasus.co.uk wrote:
I love the new website but have come across an issue: Searching for ODBC as the search term, "All Messages" gives "502 Bad Gateway"
Server-side sessions are in place. Try it again.
-- Ed Leafe
It certainly does - Thanks Ed Paul Newton
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Ed Leafe Sent: 29 April 2019 15:37 To: profoxtech@leafe.com Subject: Re: [ADMIN] Updated Website
Sent by an external sender ------------------------------
On Apr 29, 2019, at 2:24 AM, Paul Newton Paul.Newton@pegasus.co.uk wrote:
I love the new website but have come across an issue: Searching for ODBC as the search term, "All Messages" gives "502 Bad Gateway"
Server-side sessions are in place. Try it again.
-- Ed Leafe
[excessive quoting removed by server]
No more football pictures ...
__
On 29/04/2019, 15:37, "ProFox on behalf of Ed Leafe" <profox-bounces@leafe.com on behalf of ed@leafe.com> wrote:
On Apr 29, 2019, at 2:24 AM, Paul Newton Paul.Newton@pegasus.co.uk wrote: > > I love the new website but have come across an issue: > Searching for ODBC as the search term, "All Messages" gives "502 Bad Gateway"
Server-side sessions are in place. Try it again.
-- Ed Leafe
_______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/6B792FEC-732C-44B4-AC17-C3F8CEEEE438@leafe.... ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Looks good, big step up from the old one.
On Apr 29, 2019, at 3:06 AM, Alan Bourke alanpbourke@fastmail.fm wrote:
Looks good, big step up from the old one.
Thanks. Another big reason was that the old site wasn’t made in the mobile device world. This new CSS framework handles a lot of that automatically.
-- Ed Leafe
+1!
I just checked out a link to a posting - like Ted's about the Footer - and the new site looks Really Sweet! Kudos Ed!!!
-K-
On 4/29/2019 10:37 AM, Ed Leafe wrote:
On Apr 29, 2019, at 3:06 AM, Alan Bourke alanpbourke@fastmail.fm wrote:
Looks good, big step up from the old one.
Thanks. Another big reason was that the old site wasn’t made in the mobile device world. This new CSS framework handles a lot of that automatically.
-- Ed Leafe
[excessive quoting removed by server]
Hi Ed,
New site looks great. Your blog link on the home page shows a 502 error (Chrome browser running under macOS). I get a 404 error if I try to access directly.
Malcolm
On Apr 29, 2019, at 1:01 PM, Malcolm Greene profox@bdurham.com wrote:
New site looks great. Your blog link on the home page shows a 502 error (Chrome browser running under macOS). I get a 404 error if I try to access directly.
Thanks for catching that. Fixed.
-- Ed Leafe
-
Adam Buckland -
Alan Bourke -
Ed Leafe -
Kurt at VR-FX -
Malcolm Greene -
Paul Newton