How to get out if the client gives git to the project of an outdated version where there are problems with the build?

Question

Docker

ran into a problem. I don't know how to solve. the client has an auto-deploy set up that works when there are changes to git. All sites are running in the docker in Laradock. I tried to download their project from the git and deploy it - nothing happened. The project requires php7.2 version - installed it, but when I try to composer install I have problems. Also, problems arise when trying to npm install.

Even when I downloaded their entire laradock folder and ran the command to deploy the container, I had a lot of things downloaded to the computer, but there was also a lot of redness about the fact that there were no library versions at all and there were still various problems. How then to be if the images that the container uses to ensure the performance of sites can no longer be downloaded online?

It's just embarrassing. The client has such interesting tasks. and I have no way to deploy in my local environment. Rebuilding the project and putting it on a new version is also not an option - they have a lot of routes there and everything is written. and when I tried to pull on the new version of laravel, so many problems began to arise that it immediately became clear that this could not be resolved in one sitting. Perhaps I would have figured it out in a week, but you won’t take money from the client for this.

It turns out that it remains only for the client to say that I can’t do it without an experienced devops. I know how to do my job, but deploying outdated versions of projects and resolving library version conflicts is completely not my skill.

Well, there was no transfer of cases. I only know some points about the project, but I don’t know how to deploy.
But I can’t refuse either, because the client was waiting for me when I was free. we talked to him. he talked a lot about the project, we had a trusting relationship. Before that, I successfully coped with one task related to servers. Therefore, now it is not possible to say "sorry, figure it out for yourself."

Answer 1

Try to raise your local repositories using JFrog Artifactory and drop all node_modules and other dependencies there. But in the free version, you will have to be smart with the Generic repository. Support for a number of repositories is a feature of the paid version. Or do some magic with the Nexus. As a result, you will be able to build the project using old dependencies + Nexus / Artifactory can cache new ones as well. Perhaps your client or his previous developers had their own repository raised.
How about asking for documentation? Do you think you will lose your reputation for such inquiries?