lundi 11 novembre 2019

file seems to be cached. Changes aren't reflected

I have a problem in which I was working and I realized that there's an asset that is cached somewhere and now I cannot work in that file.

I had created a javascript function and it was deleted but keeps on appearing.

So far what I have tried have been:

  1. Tried on different browser even Firefox which I hadn't used it and the file appeared with the old function.
  2. Checked log history. That change was not commited. On top of that I tried git reset HEAD~1 --hard and nothing.
  3. Restart nginx, and deleted tthe log files
  4. Deleted the file. And even though I deleted it, the file keeps appearing on Chromium (the one I always use) and on Mozilla.

The configuration file of the app in nginx is the next one.

server {
    #listen 80 default_server;
    #listen [::]:80 default_server;

    # SSL configuration
    #
    # listen 443 ssl default_server;
    # listen [::]:443 ssl default_server;
    #
    # Note: You should disable gzip for SSL traffic.
    # See: https://bugs.debian.org/773332
    #
    # Read up on ssl_ciphers to ensure a secure configuration.
    # See: https://bugs.debian.org/765782
    #
    # Self signed certs generated by the ssl-cert package
    # Don't use them in a production server!
    #
    # include snippets/snakeoil.conf;

    root /home/jorge/simple/public;

    # Add index.php to the list if you are using PHP
    index index.php index.html index.htm index.nginx-debian.html;

    server_name simple.local;

    location / {
        # First attempt to serve request as file, then
        # as directory, then fall back to displaying a 404.
        try_files $uri $uri/ /index.php?$query_string;
    }

    # pass PHP scripts to FastCGI server
    #
    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
    #
    #   # With php-fpm (or other unix sockets):
        fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
    }

    # deny access to .htaccess files, if Apache's document root
    # concurs with nginx's one
    #
    location ~ /\.ht {
        deny all;
    }
}


# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/ and symlink that
# to sites-enabled/ to enable it.
#
server {
    listen 80;
    listen [::]:80;

    server_name simple.local;

    return 301 http://$server_name$request_uri;
}

I couldn't find where nginx cache files are located. I use Ubuntu budgie



via Chebli Mohamed

Aucun commentaire:

Enregistrer un commentaire