Saya penasaran, lebih oke mana untuk Elkarte: nginx murni atau Apache+nginx?
Untuk forum yang pasif (lebih banyak dibaca) performa Apache+nginx mungkin hampir setara dengan performa nginx murni.
Namun untuk forum yang sangat aktif saya rasa kok berbeda hasilnya. nginx tampaknya hanya membantu untuk visitor yg membaca pasif, sedangkan untuk member-member yang aktif menulis akan ditangani oleh Apache. Jika benar demikian, maka mending pakai nginx murni dong?
nginx murni diwakili oleh easyengine
Apache + nginx diwakili oleh serverpilot
Keduanya menggunakan PHP 7.0
IMO there is no need to run Nginx + Apache ... Just pick the one you are most comfortable with. Most of the information on the web about using one as a front end or about memory usage etc is dated information. Use the most recent version of either web server and you will be fine and hard pressed to notice a difference. Again IMO
biasanya yang pertimbangan pakai apache+nginx itu karena kompatibilitas dengan rewrite rule (htaccess) mas. dan ingin tetap merasakan manfaatnya performa Nginx. kalau saya milih murni nginx saja, apalagi ga pakai rewrite rule. :D
PS: I really thought @Spuds
understands Indonesian language. :P
LOL, you know now that you mention it, it was hard to read O:-)
You can use either or both. It doesn't matter much, really. As mentioned by @Spuds
elsewhere, he is using nginx and never look back. After using apache for 3 years, I tested that as well and nginx seems good standing on its own, a little better than apache I'd say. But that just me, as different person will have different experiences based on the way they use their server. So choose wise.
If your site handles php intensive processes such as image resizing or even a lot of image uploading, you will see a significant performance gain with standalone nginx. Nginx can load image files without involving php. Apache not so much. So much lighter on memory too. I see no advantage to backending either. It simply adds another unnecessary process.
Woah, I did'nt know it would attract international users :D
Yeah I also prefer to use standalone nginx by the way. I asked this question merely because of convenience matters, since ServerPilot does not support standalone nginx yet
We are just neighbours bro. ;)
serverpilot target market is different IMO, the users that migrated from shared hosting to VPS but doesn't want to dabble much in the management side.
agree with @kucing
, I also use ServerPilot and does a great job ;)
I am running various applications on nginx and "never look back". Among them was Drupal in various (older) versions, and at present i still an old version of SMF. Mostly well doing except for a few glitches - but that seems most probably to be a problem of PHP backward compatibility.
I am going to migrate this to ElkArte as soon there is a German translation (which does not necessarily need to be complete, the old SMF translation isn't complete either.)
as far as I know @Jorin
made most of german translations, and last time I looked to Transifex was almost complete.
/me is still working on the 1.1 repo at transifex, I think I did a mistake when I set it up and now I have to fix the mistake as well. :'(
Right, but I do not use Transifex. I don't like it and it doesn't like me. ;) I offer the translations on my support site (http://support.elkarte-hilfe.de/index.php/topic,110.0.html) and inform @emanuele
Next week I plan to install a fresh board and start to work on the translation. O:-)
Having just read the latest announcement in Jorin's support forum: how will this affect the language support for 1.1 and forthcoming releases?
Not at all, Bea. I am happy to translate future releases of ElkArte and offer the language files here. But I don't have time to work on it before end of june. O:-)
Just of curiosity: are there any incompatibilities between new and old language packs or are the latter just incomplete?
As some strings have changed there should be error messages using the old language pack with Elk 1.1 in your error log. You can ignore them though, they are not crashing any functionality. If a string is missing in the german language files, Elk should be so clever to use it from the original english 1.1 language file instead. Therefor your users may see some english texts in their german board.
But if you can wait a few weeks longer, the german language pack for 1.1 should be ready. O:-)
That's a great work. I haven't started on 1.1 yet. 1.0 also is not 100% ready though is usable.