Search the Community

Showing results for tags 'nginx'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Found 13 results

  1. Now I add a PW on my domain. It runs OK. Then I have a second demo PW running under /demo/ subdirectory. and adding these code to nginx rewrite: location /demo/ { try_files $uri $uri/ /demo/index.php?it=$uri&$args; } Then I access the subdirectory's homepage(/demo/) is OK, other page return a 404 error. But I replaced the other cms to /demo/, It's really OK. Why? How to fix these errors?
  2. Hello Everyone, Sorry that I have not been on the forums much of late. As my development team moves to use ProcessWire as our main cms tool for clients. We have needed to make sure that ProcessWire works on nginx platform. We use both apache and nginx, we found as many already have that nginx is faster and easier to configure. It scales well and when you really need speed it is a great solution. Anyways with all that being said ProcessWire was surprisingly easy to configure for nginx and did not require adding or modifying any code. Using the same "try_files" directives used for Wordpress and Dupral I was able to run it under nginx, here is a sample config: upstream php { server unix:/tmp/php-cgi.socket; server 127.0.0.1:9000; } server { listen 80; server_name hostname; root /websites/path/to/processwire; index index.php; try_files $uri $uri/ /index.php?it=$uri&$args; location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; include fastcgi.conf; fastcgi_intercept_errors on; fastcgi_pass php; } } There are a few things that still need to be done like protecting the wire and certain directories like assets but so far everything looks to be working correctly. If ProcessWire has a test suite, I could run it against this server to see if everything is functioning properly. I think that advertising the fact that ProcessWire works under nginx would greatly help to attract more eyes to the project(not that it isn't doing great already) and to give options to hosting and scalability. If you would like help working on this for official support of the platform, perhaps with adding detection algorithms to the install or anything else that is needed, I would be glad to help. Anyways I hope someone finds this post useful.
  3. Hello everyone, I've been fiddling around a lot lately with docker containers for my local development on a linux machine. Tried many different options, also readily available processwire images and tutorials from the forum. But never got it right. Mainly because of permission issues with docker volumes. That is a tricky part on linux machines whereas on OSX it doesn't seem to be an issue. Then I discovered http://www.wordpressdocker.com/. And the setup with nginx as a proxy that routes requests to separate containers with the actual site install appealed to me. The whole thing sits on top of alpine linux containers which are really lightweight. So I decided to give it a try. And, first time since experimenting with docker, I got a running PW install. Rewriting was not working until I adjusted the nginx config. Now I have a fairly complex PW site running in a container. Everything is working, image upload/editing etc. So I'm really exited, especially since the dev site is now blazing fast compared to my old vagrant virtualbox vm setup. Honestly, I don't really understand everything that is happening behind the scene. But I managed to adjust the original files and build a new image that works with PW and doesn't have all the WP stuff. The nginx config I took from https://github.com/elasticweb/nginx-configs/blob/master/configs/processwire-2.conf Not sure if it covers everything for PW3 as well. I would very much appreciate if someone who is more in the know than me could take a look. All files for building the docker image are here https://github.com/gebeer/alpine-php-processwire A working image here: https://hub.docker.com/r/gebeer/alpine-php-processwire/ Documentation is kind of lacking. I took over quite a lot from the original project. But following the github README and the original documentation should get people started who have a little experience with docker already. If someone needs a more in depth step by step tutorial for setting things up, let me know and I'll put something together.
  4. Hi, I'm having some issues with PW after a NGINX error, I'll try to elaborate: 1) My nginx site conf file went corrupt. 2) try to recreate it using: https://processwire.com/talk/topic/275-processwire-on-nginx/ 3) All my urls are accesible using '/' or without it. 4) I have urls that doesn't work without the / at the end, the url is dynamic (I check for the segments) Ex: "www.url.com/something/countries/usa" works! "www.url.com/something/countries/usa/" works! "www.url.com/something/countries/mexico/" works! "www.url.com/something/countries/mexico" doesn't work I assume it has something to do with my nginx, it only happens with the same country, in fact if you use a country that doesn't exist it just redirect you to the main url, but in 'mexico' case it just return a 404. Any ideas??? edit: something I forgot I testing adding it a backslash to all urls but the backend has some troubles when it comes to saving.
  5. Hi all. I have a successfully installed and running PW site on NGINX. It all went well and easy thanks to the hints and tricks in some thread. However even though I hits the frontpage nicely then any navigation to anything on the site returns a 404 - even the admin panel URL. I suspects that it does not properly pass the URL to processwire but is instead trying to move to a directory. Any ideas? edit: it works without subdirectories, this my config with subdirectory tryna to solve it. not work though root /var/www/test.test/html; index index.html index.php; server_name test.test access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; error_page 401 403 404 /404.html; # ----------------------------------------------------------------------------------------------- # This location processes all other requests. If the request is for a file or directory that # physically exists on the server, then load the file. Else give control to ProcessWire. # ----------------------------------------------------------------------------------------------- location / { try_files $uri $uri/ /index.php?it=$uri&$args; } location /pw { try_files $uri $uri/ /pw/index.php?it=$uri&$args; }
  6. try to get PW 3.0.30 up on Ubuntu 16.04 / nginx version: nginx/1.10.0 (Ubuntu) the installation works fine but afterwards only default page displays, any other throws a 404 error page. we looked at the PW on Ngnix on Howtoforge any idea, thanks nginx access.log shows: server { listen 80; server_name processwire; index index.php index.html; root /var/www/html/promowall.ch/public_html/ProcessWire-devns; access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; default_type application/x-php; ### SECURITY - Protect crucial files location ~ /\. { deny all; } location ~ /(COPYRIGHT|LICENSE|README|htaccess)\.txt { deny all; } location ~ ^/site(-[^/]+)?/assets/(.*\.php|backups|cache|config|install|logs|sessions) { deny all; } location ~ ^/site(-[^/]+)?/install { deny all; } location ~ ^/(site(-[^/]+)?|wire)/(config(-dev)?|index\.config)\.php { deny all; } location ~ ^/((site(-[^/]+)?|wire)/modules|wire/core)/.*\.(inc|module|php|tpl) { deny all; } location ~ ^/(site(-[^/]+)?|wire)/templates(-admin)?/.*\.(inc|html?|php|tpl) { deny all; } ### GLOBAL REWRITE location /ProcessWire-devns { try_files $uri $uri/ /index.php?it=$uri&$args; } # pass the PHP scripts to FastCGI server on local socket # location ~ .+\.php((/|\?).*)?$ { fastcgi_pass unix:/run/php/php7.0-fpm.sock; fastcgi_index index.php; fastcgi_split_path_info ^(.+\.php)(.*)$; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_param PATH_INFO $fastcgi_path_info; fastcgi_param HTTP_MOD_REWRITE On; include fastcgi_params; } # redirect server error pages to the static page /40x.html error_page 404 /404.html; location = /40x.html { root /usr/share/nginx/html; } # redirect server error pages to the static page /50x.html # error_page 500 502 503 504 /50x.html; location = /50x.html { root /usr/share/nginx/html; } }
  7. HELLO! Is anyone running a http/2 setup in production yet and have any strategies / experiences they can share? I'm currently running on Ubuntu with DigitalOcean | nginx with serverpilot.io (and they now offer https/2 support)
  8. Hi, I don't know if this is the right section for this but I collected some thoughts and a kind of manual about how to increase the performance of your website under load with nginx and fastcgi_cache. At best, this could be a kind of ProCache for nginx users, as not everyone is using Apache and thus not able to use ProCache on their sites. Additionally, this solution comes with the benefit of server side mobile detection and selective caching. http://svn.matthiashaak.com/website-performance-with-processwire-nginx-and-fastcgi_cache/ Please let me know your thoughts or questions about this. Be aware however, that with this solution you end up serving static pages, so no hooks or PHP functions will be called. I am currently working on a module that eases the cache purging, so kindly be patient if you need this. "Wait, and thou shalt receive"
  9. Hello, I'm deployed multiple pw sites already, all with nginx. This time I need to have multiple pw sites for a domain, every one of them under a subdirectory. I've been trying many things, every time I get 404 or 500 errors on /directory/processwire ( the /directory/ works, other pages not ). Did someone already managed to get that working ? PS : Apache is not an option
  10. Story: https://processwire.com/talk/topic/9250-what-should-i-do-to-make-pw-to-work-with-a-reverse-proxy-cache/ After a few days of reading documentation, I got processwire to work with nginx reverse proxy cache. This is not a tutorial on how to install server software. A working nginx config copy will be posted on next reply. Ubuntu 14.04.1 x64 Nginx 1.4.6 apache 2.4.7 mysql 5.6.19 php 5.6.6 (php5-fpm) A new copy of content will be fetched instantly. A screencast of this demo
  11. Just spotted a PW on Nginx installation tutorial on how-to-forge. I quite like that site - find it useful from time-to-time - so big thanks to Falko Timme for taking time to write it up. Nice
  12. Hi, I know there have been a lot of talks on providing official support for nginx (Link - http://processwire.com/talk/topic/275-processwire-on-nginx/) however, official support for it is not mentioned in the current roadmap (Link - http://processwire.com/about/roadmap/) I was wondering if this is likely to happen anytime soon. Any thoughts?
  13. Is anyone tried using nginx as frontend proxy to serve static content and apache as backend. I am having trouble in image upload path as now upload folders are created with hyphens in start so getting not found error. Any sample conf file for frontend proxy I have seen conf file when nginx used alone but that not helping