I recently upgraded the wiki to version 1.23 (new LTS version). As usual Mediawiki made a very good work, no problems during migration using Git, everything is working.
No major visual changes between the previous version 1.22 and this one. I didn’t had to touch anything on my JS, CSS or configuration! Great!
I encountered an issue with my GoogleSearch extension and made the changes to make it work again. So a new version (0.
Last week, have been faced on a big sniffing issue on my wiki. The guy wanted to download all my wiki content. In reality I do not really care as it is open, free for read and contribution is welcome. However, the current VM where the blog and wiki are running didn’t support aggressive sniffing that this guy made. That’s why CPUs were at 100% of usage because of PHP requests, PHP-FPM was overloaded (reached my configuration limits).
My last post was about existing alternatives to Dropbox. I also mentioned that I was trying Seafile.
I’m running now Seafile since a few days now and it works without any issues. The Linux and Android clients works very well. I just hope a sync feature in the Android version will appear. Regarding the web version, there are all attending collaboration features and that’s great. Seafile supports file versioning and trash bin.
Some of my readers asked me more clarification on where information’s could be find on my site. I wanted to make it clear and have a welcome page to make things easier.
Some of my readers asked me more clarification on where information’s could be find on my site. I wanted to make it clear and have a welcome page to make things easier.
So you can take a look the result:1
If you want to easily build a static webpage with parallax effect, you can try the Cool Kitten framework. It is a young project that already have cool stuffs like grids solution, responsive design etc…It uses Normalize.css, jQuery Easing Plugin and Stellar.js.
You need nodejs to minify CSS but do not need nodejs server to run it, as it is static HTML pages.
In a few days, I’ll show you my usage.
Yesterday a colleague (Dimitri) tested a tool on this blog. He informed me that Varnish was disabled and PageSpeed may be the cause as this is the last modification I’ve made on the server.
After verification he was totally right ! By default, PageSpeed disable cache by serving HTML files with:
Cache-Control: no-cache, max-age=0 After reading the PageSpeed documentation on that topic, it is clear: PageSpeed needs to know how to purge the cache as it rewrites a lot of elements and it has the control instead of the application.
Following a previous post, I’ve enabled PageSpeed on both wiki and blog deimos.fr.
What I can say is, it’s very important to take the time to test every optimizations you want to add. I experienced for example issues on silly things like :
# Optimize browser rendering pagespeed EnableFilters lazyload_images; Some images weren’t shown if you didn’t refresh once again your page browser. I only had this problem on the blog and not the wiki.