New answers tagged nginx
1
In your nginx configuration file (nginx.conf) check who is the user. In your nginx.conf the user directive should at the top. Then check if the directory /var/www/www-root/data/www/mysite.com/ belong to that user.
Now lets say your user in nginx is www-data and the files in /var/www/www-root/data/www/mysite.com/ belongs to root. You should run a command to ...
1
your development must be separated from live. it is better for security and maintenance.
just copy your magento installation to another account / home folder.
copy nginx config, update root, domain and base url.
in varnish you need to add either one:
full domain bypass:
if (req.http.host ~ "^dev\.example\.com$") { return (pass); }
or parameter ?developer ...
0
What about a pure nginx solution with this double map ?
First, for the web site (thanks @MagenX)
map $request_uri $MAGE_RUN_CODE {
default website1;
~^/website1/.* website1;
~^/website2/.* website2;
}
A second for the new request uri
map $request_uri $REQUEST_URI {
default $request_uri;
"~*^/(website[0-9])(?<p>.*)" $p;
}
And ...
1
Magento has configurations for both Apache and Nginx ready to use for production.
The reason why Magento team offer these configurations out of the box is for security reasons.
If you check the folder update you will notice that there are these files/folders
app -> folder
dev -> folder
pub -> folder
vart -> folder
.gitignore -> file
.htaccess -> file
...
1
This have been done in the same wrong way by many folks:
NGINX config with pub as webroot (great)
web URL includes pub in URLs (bad)
To explain it simply why it doesn't work for you: NGINX root is pub directory, so anything that starts with / is already in pub. When you put links that include pub, they are trying to load /path/to/pub/pub/some/file (which ...
1
Is it not loading because of a 404 ?
Did you check if the file generation to pub/static works, means is it an issue with the loading, or already the generation ?
Is your magento installation in production mode, and if yes, did you regenerate the static content using php bin/magento setup:static-content:deploy?
Did you check the file and folder permissions ...
Top 50 recent answers are included
