Where are blueprints stored on Windows?

Hi, I would like to grab the blueprint I made on one computer and use it on another. I’m assuming that these blueprint files are .zip files stored somewhere on Windows? Can someone please provide the path? I did a search on local system and cannot find them :frowning:

OK, I finally found my own answer and thought I’d share in case someone else would like to know!

The blueprints are .zip archives stored in a hidden “blueprints” folder here:

C:\Users\xxx\AppData\Roaming\Local by Flywheel

xxx being your user name of course

1 Like

Yup, that’s correct!

One nice shortcut you can use in Explorer and Cmd.exe is %AppData%\Local by Flywheel.

%AppData% points to C:\Users\xxx\AppData\Roaming.

1 Like

Oh… except one thing… not sure if this is a bug… after pasting my blueprint in the second computer’s blueprints folder and trying to create a site based on that blueprint, it threw up an error halfway thru provisioning process about being unable to edit host file.

so is it possible that one cannot carry their blueprints from one machine to another simply by dropping the files in the blueprints folder? maybe something else is done in the backend when a blueprint is created the proper way thru LOCAL?

can someone try this out on Windows computers and let me know their results please? otherwise I will report it as a bug…

Blueprints should work interchangeably without a problem.

Can you try creating a site on that computer without a Blueprint and see if you run into the hosts file issue?

I can confirm that I was able to create a site without error (from scratch). That’s how I did it the first time, before I discovered the file location of the blueprints.

On another note…on both machines when I try to shutdown Windows, I get a bluescreen with a warning that VitualBox is active and has open connections (or something like that) - and I always have to choose Shutdown Anyway. Is this a bug or something your team is working on? I never like to force shutdown things running in the background like that, but I assumed that exiting LOCAL would also shut down everything needed for a graceful shutting down of Windows…

1 Like