I might be in the wrong place to post this, but just wanted to add that I just tried the process of creating a non-WP site in Local by adding a new Local site and then deleting all WP files. At the end of that, in the Local database tab, it's still apparently looking for app/public/wp-config.php to find the database. Even though I manually dumped and then imported the database I want to use, I can't figure out how to connect to it with Local.

Mike Hemberger: yes a tutorial for this would be great

Clay Griffiths: Thank you for keeping this under review and maintaining the likes. I second what Jason Adams is saying. It would be a game changer for me and allow for Local to be my only source for local dev. I'm not sure how Pro could be utilized with other CMS but it would certainly make it more attractive to go Pro if I could use some/all features no matter the type of site I'm developing and not just Wordpress sites.

Jason Adams: Appreciate the response! I'd hate to lose the votes as you mentioned.

I'll go ahead and re-open this and mark it as "Under Review." It's something we've been chatting about on the team but haven't officially committed to yet.

Clay Griffiths: While is this greatly appreciated, I feel like the actual patch does not really get at the heart of this Canny post. Right now WordPress is the only first-class citizen within Local. Other CMS don't break Local, at best — which is what that latest patch is ensuring. This post is asking that other CMS options become a first-class citizen as well (see my post below, starting with "As mentioned in my merged post".

Should we open up a new Canny post for that? But then we lose the voter count and have to start over. 🤷‍♂️

Hi all, importing non-WordPress Local exports and creating sites using non-WordPress Blueprints is now possible in Local 5.7.4 (https://localwp.com/releases/5.7.4). Thanks again for your patience regarding this!

Looks like this is a bug in general when removing sites from local and then trying to create new ones...the original database servers are still running from the deleted sites. So there's a conflict when creating new sites that use the same port numbers as the deleted sites.

Should Local instead be deleting the database servers when sites get removed? (I should probably be posting this somewhere else?)

Clay Griffiths: fantastic! i got the beta and going to test it.

Just FYI when I try to provision new site with the Beta, it fails because a database already exists from Stable version. Even if I uninstall Stable, I still can't provision a new site.

If I manually connect to the existing mysql server from Stable version, and delete the local database, then I can successfully provision new sites.

Joel Szwarga: That post was intended for the beta release channel. Sorry for the confusion there!

If you wish to get access to the 5.7.3 beta, you can download it here: https://localwp.com/community/t/local-beta-5-7-3/21823 (see https://localwp.com/community/t/introducing-local-beta-group/15669 to get access).

5.7.3 stable is still slated to be released this week. 😃