How to configure git staging server? And is it appropriate?

Question

Current situation

My team is based in Singapore. We needed to install the Django web application in China for speed reasons for the corporate client to use inside the network.

So we did it like that.

What's wrong?

The git clone is painfully slow, and our files → 50 mb.

What have you tried?

I am thinking of setting up an intermediate server in Hong Kong to reduce latency for git clone.

Perhaps the chart is off a bit.

We used CircleCI. I think we can get CircleCI to have the following setup.

Whenever GitHub received an update in the main branch of our repo, the Hong Kong server will pull out the latest copy of the main gearbox.

For a server in China, I think I can configure it to git pull every day at several rush hours using cronjob.

So what is your problem?

I can easily configure google for git steps like this https://git-scm.com/book/en/v1/Git-on-the-Server-Setting-Up-the-Server

My concern is whether the approach described above makes sense.

If that makes sense, then my question is , how do I configure CircleCI what?

Our team's experience with CircleCi is limited to working with GitHub and Heroku. We have never used it with GitHub and the standalone server on which we will work.

Answer 1

You can use a small clone on a server in China to improve git clone performance.

For example, if you want only the latest version:

git clone --depth 1 <repository-url>

You say that your files are> 50 MB in size, so to clone them you still need to clone if there are many, but at least you upload them only once.