-
Notifications
You must be signed in to change notification settings - Fork 78
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
Enhance documentation for initial setup #375
Comments
Thanks for sharing this. It is the first time that I hear about issues like that. The error looks like it could be due to an instable or slow connection. This repo is definitely not large and I had a lot of occasions where I set this up with people also in flaky conference networks where cloning nextcloud-docker-dev was never an issue. Do you have more insights why disabling compression would lead to more stability there, as I would rather expect it to become slower then. |
Hi Julius,
It's definitely linked to network problems. Unfortunately not everyone have access to stable network. Even living in one of the most advanced city in the world (aka Shanghai, China).
Its seems Github is having some restriction with Chinese Great Firewall.
Strange enough, I can access the Github repository in my browser without proxy or VPN. But "git clone" cannot establish TLS connection.
I have a VPS in Hong Kong. I setup shadowsocks-rust. All apps can use this connection with no problem.But git clone keeps failing randomly after few mega bites.
Randomly I was able to dowload your initial repository. But bootstrap script failed and cannot be run again.
The reason I use a directory copy to at least have a safe backup of first step.
All the best and happy chinese new year
Denis
***
Le jeudi 30 janvier 2025 à 15:44:01 UTC+8, Julius Knorr ***@***.***> a écrit :
Thanks for sharing this. It is the first time that I hear about issues like that. The error looks like it could be due to an instable or slow connection.
This repo is definitely not large and I had a lot of occasions where I set this up with people also in flaky conference networks where cloning nextcloud-docker-dev was never an issue.
Do you have more insights why disabling compression would lead to more stability there, as I would rather expect it to become slower then.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Being struggling for 2 days in building the repository, I would suggest to enhance install documentation.
Main issue is repetitive "fetch-pack: unexpected disconnect while reading sideband packet" during git clone.
Either to load initial https://github.com/juliusknorr/nextcloud-docker-dev. Or when running bootstrap script.
Documentation should make it more clear that the steps:
git config --global core.compression 0
git clone --depth 1 https://github.com/juliusknorr/nextcloud-docker-dev
git fetch --unshallow
Recommand to make backup copy nextcloud-docker-dev
cp -r nextcloud-docker-dev nextcloud-docker-copy
before to run bootstrap script
This allow to restart without struggling again to download repository in case of failure during execution of bootstrap scrip.
Also the way to edit bootstrat script to make git clone safer. Or provide an alternate bootstrap script to make git clone safe
The text was updated successfully, but these errors were encountered: