I have installed Varnish accelerator with Apache webserver for Magento installation.
Can any body suggest the best default.vcl (/etc/varnish/default.vcl) configuration for this ?
Any help appreciated.
Thanks.
Obiously you didn't Google this, atleast look for the solution yourself before you come to SO.
When I googled "Magento Varnish" I came up with this first links that is a FREE extension that contains the default.vcl file that you need:
http://www.magentocommerce.com/magento-connect/pagecache-powered-by-varnish.html
If google did still guide you here:
Magento does by now offer a default VCL files within the depths of their GIT repository.
for Varnish 4.x
https://github.com/magento/magento2/blob/2.3/app/code/Magento/PageCache/etc/varnish4.vcl
for Varnish 5.x
https://github.com/magento/magento2/blob/2.3/app/code/Magento/PageCache/etc/varnish5.vcl
for Varnish 6.x
https://github.com/magento/magento2/blob/777b0b0a0950b819991fda239793c91c966254be/app/code/Magento/PageCache/etc/varnish6.vcl
Related
I little bit confused with my server. Its not returning cache-control headers with varnish and if I try to add cache control headers manually via .htaccess then varnish is not returning appropriate headers for HIT or MISS and Age numbers.
I also do not know how to edit /etc/varnish/default.vcl ?
I am using a VPS and details:
cPanel Version 72.0 (build 10)
Apache Version 2.4.34
PHP Version 5.6.37
Architecture x86_64
What can I do? I have tried other similar solutions and they did not work maybe outdated or i do not understand what to do?
It was happening because of imperfect/imcomplete articles posted on the web.
I found complete installation detail on the github and fixed the issue
https://github.com/apache/incubator-pagespeed-cpanel
Its very difficult for a newbie guy to know the your installation article is incomplete and leave you in the middle to installation.
This is a very simple question, but I have struggled for two days to start up my WebObjects on a deployment Debian server. Everything has worked fine so far with Eclipse and Direct Connect, and an apachectl -M shows that the webobjects module (http server) is installed, running and shared. But when I try to run something as simple as a Hello World the browser returns a 404.
My applications are in /usr/share/webobjects/Library/WebObjects/JavaApplications/
Any pointers as to how I should configure (symbolic links and .conf entries) to make this work?
Much appreciated.
Luis
Have you had a look at the Deploying on Linux page on the WOCommunity wiki? If that doesn't help, you may need to post the relevant sections of your httpd.conf here for inspection.
It would be really helpful if some one could advice me how to include mod_autorotate in apache modules working in linux.
Follow the basic instructions at the authors website?
http://www.poptart.org/bin/view/Poptart/ModAutorotate
Currently, I can push my repositories to CentOS server (example.com) through ssh to /var/lib/mercurial-server/repos/SOMEREPO using hgadmin.
Is there a way to access SOMEREPO via example.com/SOMEREPO ?
There are a lot of ways how you can publish your repositories.
If you're familiar with apache, the probably simplest solution is to use hgweb.cgi which is a cgi script that comes with the mercurial distribution.
An in-depth step-by-step guide how to setup hgweb can be found at the mercurial wiki . Since you mentioned CentOS, you probably want to check out the hgweb setup guide for RHEL4.
If you're looking for more complete web-based tools to manage your repositories you may want to look into SCM-Manager or RhodeCode.
Yes - Google abounds with information about configuring Apache to support SSI.
But unfortunately, I still cannot seem to get it right.
My questions:
Can anyone furnish me a full-fledged example config file that enables SSI on an Apache server?
Also can you please tell me where I should drop this config file (i.e. which
directory)?
Apache probably wouldn't run if you didn't already have a fully-fledged config file. Try an
apachectl configtest
and see what happens.
My site is hosted at 110mb.com.
Interestingly enough, here is the solution:
Rename all files which have server-side includes to *.shtml.