New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON encrypted/compressed over HTTPS #4
Comments
This is the output I get:
|
Hi @cameronwilby, there a feature, i lack to explain on a tutorial to create your own mirror, next few days i fixed this problem. The mirror creation save all data as .gz to save disk space, you need to enable reverse gz decode when a client ask for the decompressed version. To do this, change you nginx configuration of gzip_static and gunzip as is:
Source: |
@webysther that did the trick, thank you! Here is the nginx config I ended up with:
|
Great @cameronwilby! Another tip is using a machine with 2GB at least of memory. With that all metadata keep to the memory helping the nginx and disk to not be consumed. |
Good to know, I went with the 2GB droplet on DigitalOcean 👍 Thanks again @webysther, awesome work. |
After deploying this app to a DigitalOcean droplet I was able to connect my local composer instance and install dependencies.
After enabling HTTP on the server using LetsEncrypt, composer is no longer able to fetch
package.json
as it appears encrypted/compressed.I have tried enabling/disabling gzip to no avail.
Update: the file is encrypted/encoded on the server when opened with
sudo nano package.json
.The text was updated successfully, but these errors were encountered: