Support

My test server at the office is an Ubuntu Server 12.04 machine with NginX. That three years old triple-core AMD with the ageing SATA I, slow (5000rpm) hard disk is flying. I know what you mean!

Regarding your question, nothing special is required. Just enable Admin Tools' secret administrator URL parameter. It doesn't use .htaccess. Its PHP code runs through the System - Admin Tools plugin.

Regarding the .htaccess Maker, I am working on an NginX configuration maker in a similar vein. If you're interested to see how the .htaccess features translate to nginx.conf directives, take a look at https://akeeba.assembla.com/code/master-htaccess/git/nodes/master/joomla.nginx.conf This is what the new feature will be based on.

Thank's Nicholas. It's good to know that you working on it and thanks for the link - awesome! I'll give it try on testing environment.

Great! Please do. I only have a test server with NginX. I'd be more comfortable with my nginx.conf if I knew it's also tested by someone other than me.

I need to say again that you providing the best and fastest support in Joomla! world :).

Thank you :)

I'm moved two Joomla websites from instance with Zend Server Community Edition to... Nginx instance with some performance tweaks and so far so good. It seems that charges for used resources will go down. It's just little bit different to configure it so need to learn little bit. I'll test some various Joomla scenarios with Akeeba Backup and Admin Tools on Nginx during the next few days.

I hear ya! NginX scales much better on high request environments. Fotis (of K2) did a great presentation on the topic of high performance servers in Joomla! Day Greece 2012 and this gave me the incentive to start working on NginX. Damn! It's seriously FAST! Akeeba Backup has no problem on it. The contrary. It is slightly faster (only slightly because the bottleneck is the hard disk). Admin Tools works perfectly, except the .htaccess Maker and administrator directory password protection of course. Yes, configuration is slightly different... but it's so much easier! What requires two long, cryptic lines in Apache only takes a short line in nginx.conf. Once you get the hang of it you start wondering "seriously, what were Apache's mod_rewrite developers thinking?". Yep, NginX is cool.

BTW, NginX also has some interesting security extensions. I have yet to find the time to seriously test them, but judging from what I'm reading they seem to be kicking serious ass out of the box. They even have a "learning mode".

Hi Kamil,

I just want to know if my setup caused any functional issues on your sites. Your extensions mix seems very good. I can see a few extensions that might break (WidgetKit, Kommento) and you'll need to add exceptions for them. I see a few which will prove the not very well tested SEF URL part (RS SEO, sh404SEF). It sounds like a brilliant experiment :)

Regarding Joomla! 2.5 vs 3.0, it really doesn't matter which Joomla! version you use. The rules are designed to work with Joomla! 1.5, 1.6, 1.7, 2.5, 3.0 (and I suspect all 3.* and maybe all 4.* versions of the CMS). As for which one to use on a live site, always stick with the LTS Long Term Suport (.5) releases. All Joomla! .0, .1 and .2 releases are STS Short Term Support releases, not to be used on production sites. I have changed the interface and wording in Admin Tools to make it clear before someone tries to upgrade Joomla!. Better be safe than sorry ;)