Does the package at:
http://nginx.org/packages/mainline/ubuntu/dists/bionic/
contain the instruction to create all the needed config files and folders?
Having managed to go from 1.14 to 1.17, I find anomalies: at least one
missing folder and its files, undeleted files with the suffix '.deleted',
e
> Where is the Bionic repo?
>
> If you are referring to the default repository for all things Linux Mint,
> there
> was only Nginx 1.14.
I mean the nginx bionic repo (here you can see the available Ubuntu versions
http://nginx.org/packages/mainline/ubuntu/dists/ )
But it seems you have alread
Where is the Bionic repo?
If you are referring to the default repository for all things Linux Mint,
there was only Nginx 1.14.
Anyway, as is always the case, something went wrong. I don't have a
'modules-available' directory, and all the items in 'modules-enabled' end in
'.removed' with link (bro
> E: The repository 'http://nginx.org/packages/ubuntu tricia Release' does not
> have a Release file.
> N: Updating from such a repository can't be done securely, and is therefore
> disabled by default.
> -
> Are there any other instructions available to get Nginx 1.17 downloaded?
You should p
In the file:
/etc/apt/sources.list.d/nginx.list
I changed:
deb https://nginx.org/packages/mainline/ubuntu tricia nginx
to:
deb https://nginx.org/packages/mainline/ubuntu bionic nginx
Then the "apt-get update" worked.
However, I used the Mint Software Manager to install Nginx, but the progress
in
So I try the Stable release:
-
Err:12 http://nginx.org/packages/ubuntu tricia Release
404 Not Found [IP: 95.211.80.227 80]
E: The repository 'http://nginx.org/packages/ubuntu tricia Release' does not
have a Release file.
N: Updating from such a repository can't be done se
I get the following lines when running :
sudo apt update
according to the instructions on this page:
https://nginx.org/en/linux_packages.html
-
Err:10 http://nginx.org/packages/mainline/ubuntu tricia Release
404 Not Found [IP: 95.211.80.227 80
Well, figured it out... I swear I tried this yesterday, but maybe I
didn't or my configuration was incomplete...
If you use "gzip_static always;" in combination with the below
statements, it works correctly! It sends the compressed response as
expected, and will decompress on-the-fly when necessar
I did a lot of googling and only came up with answers from many years
ago, or unanswered questions. Maybe I'm just not using the right
search keywords, so I figured I would ask the following
Here's my scenario... I have a bunch of static html files that would
be served directly via nginx.
Is
