Duplicate site with API

[brunocc]

Hi,

Is there a way to duplicate a site using API ?
In my usecase, I configure a site with my private gitlab repository and then need to duplicate the site with just a different environment variable and domain.
I would like them to deploy automatically when I commit/push to that repository.

Best regards

[hillary]

Hey there, @brunocc

Thanks for reaching out! Have you seen this thread? I think it may help get you on the right track:

Is it possible to copy a deployment from one site to another?

Hi, @feedm3. There are several possible approaches. Build and deploy at Netlify but don’t publish by locking the current deploy. After the checks are completed, only then publish the deploy. Do your build in a local or third-party build system and then use the Netlify CLI tool to manually deploy the build in the third-party. Build and deploy one one site and then download and manually upload that deploy to the production site. For option 3 above, you can download the deploy using the button s…

Let us know!

[matus]

I don’t think this answers the question.
Is there a simple way to duplicate/copy over all the site configuration to the new site?

[fool]

Like many things, the answer is “it depends”.

At a high level, no. There is no “create an exact copy of any site” API call. And in fact some settings are probably not “Create”-able, but must be activated with one call and then configured with another. You will spend substantial time trying to reverse engineer exactly how to configure domain aliases and other site settings such as large media, permissions, notifications, etc. Creating a generic site is easy (Netlify API documentation); creating a site with many specific settings is hard, nonintuitive (some settings can be passed to the siteUpdate call, others have to be passed to the updateSite or createSiteSnippet calls), and our docs do not attempt to address that use case.

But, as far as how your site builds and some settings on it - things like asset optimization, environment variables, redirects, etc - you can use config as code: netlify.toml! This file lets you control how and what to build, what variables to set, what asset optimizations, redirects, and headers a site needs. All in one file, that is intended to be used this way. Here’s the docs on it:

File-based configuration

As far as “how you populate the toml with your values on gitlab and trigger the creation”, not sure about that. You might consider using the Deploy to Netlify button - which leverages the netlify.toml to set custom variables a public repo: Create deploys | Netlify Docs