Remove Tauri

Author: simonhamp

public/funding.json

@@ -19,19 +19,14 @@
             "url": "https://nativephp.com/"
         },
         "repositoryUrl": {
-            "url": "https://github.com/nativephp/laravel",
-            "wellKnown": "https://github.com/nativephp/laravel/raw/main/.well-known/funding-manifest-urls"
+            "url": "https://github.com/nativephp/desktop",
+            "wellKnown": "https://github.com/nativephp/desktop/raw/main/.well-known/funding-manifest-urls"
         },
         "licenses": ["spdx:MIT"],
-        "tags": ["php", "laravel", "electron", "tauri"]
+        "tags": ["php", "laravel", "electron"]
     }],
     "funding": {
         "channels": [
-            {
-                "guid": "github-sponsors",
-                "type": "other",
-                "address": "https://github.com/sponsors/simonhamp"
-            },
             {
                 "guid": "open-collective",
                 "type": "other",

resources/views/docs/desktop/1/digging-deeper/broadcasting.md

@@ -5,7 +5,7 @@ order: 100
 
 # Broadcasting
 
-NativePHP facilitates event broadcasting of both [native events](#native-events) (emitted by Electron/Tauri) and
+NativePHP facilitates event broadcasting of both [native events](#native-events) (emitted by Electron) and
 [custom events](#custom-events) dispatched by your Laravel app. You can listen to all of these events in your
 Laravel application as you normally would or in the [JavaScript](#listening-with-javascript) on your pages.
 

resources/views/docs/desktop/1/digging-deeper/child-processes.md

@@ -29,7 +29,7 @@ application is running on (Mac/Linux vs Windows).**
 **Where possible, you should explicitly reference binaries by their full path name, unless you can reliably assume that
 the executable you're trying to spawn is available in the user's `PATH`.**
 
-Child Processes are managed by the runtime (Electron/Tauri) but are fully accessible to the Laravel side of your
+Child Processes are managed by the runtime (Electron) but are fully accessible to the Laravel side of your
 application.
 
 ---

resources/views/docs/desktop/1/digging-deeper/databases.md

@@ -40,7 +40,7 @@ You do not need to do anything special to configure your application to use SQLi
 In [development](/docs/getting-started/development), your application uses a database called `nativephp.sqlite`
 which is created in the build directory.
 
-NativePHP forces your application to use this database when it is running within the Electron/Tauri environment so that
+NativePHP forces your application to use this database when it is running within the Electron environment so that
 it doesn't modify any other SQLite databases you may already be using.
 
 ## Migrations

resources/views/docs/desktop/1/getting-started/debugging.md

@@ -19,13 +19,13 @@ This means that while some issues can be solved within NativePHP it's also very
 ### The layers
 
 - Your application, built on Laravel, using your local installations of PHP & Node.
-- NativePHP's development tools (`native:serve` and `native:build`) manage the Electron/Tauri build processes - this is
+- NativePHP's development tools (`native:serve` and `native:build`) manage the Electron build processes - this is
   what creates your Application Bundle.
 - NativePHP moves the appropriate version of a statically-compiled binary of PHP into your application's bundle - when
   your app boots, it's _this_ version of PHP that is being used to execute your PHP code, not your system's version of
   PHP. 
-- Electron & Tauri use suites of platform-specific build tools and dependencies - Electron's ecosystem is mostly
-  Javascript based, Tauri's is mostly Rust based. Much of this will be hidden away in your `vendor` directory.
+- Electron uses a suite of platform-specific build tools and dependencies - Electron's ecosystem is mostly
+  Javascript based. Much of this will be hidden away in your `vendor` directory.
 - The operating system (OS) and its architecture (arch) - you can't build an application for one architecture and
   distribute it to a different OS/arch. It won't work. You must build your application to match the OS+arch combination
   where you want it to run.

resources/views/docs/desktop/1/getting-started/development.md

@@ -20,7 +20,7 @@ This is known as 'running a dev build'.
 
 ### What does the `native:serve` command do?
 
-The `native:serve` command runs the Electron/Tauri 'debug build' commands, which build your application with various
+The `native:serve` command runs the Electron 'debug build' commands, which build your application with various
 debug options set to help make debugging easier, such as allowing you to show the Dev Tools in the embedded web view.
 
 It also keeps the connection to the terminal open so you can see and inspect useful output from your app, such as logs,

resources/views/docs/desktop/1/getting-started/installation.md

@@ -41,7 +41,7 @@ php artisan native:install
 ```
 
 The NativePHP installer takes care of publishing the NativePHP service provider, which bootstraps the necessary
-dependencies for your application to work with the runtime you're using: Electron or Tauri.
+dependencies for your application to work with Electron.
 
 It also publishes the NativePHP configuration file to `config/nativephp.php`.
 

resources/views/docs/desktop/1/getting-started/introduction.md

@@ -89,7 +89,6 @@ NativePHP wouldn't be possible without the following projects and the hard work
 
 - [PHP](https://php.net)
 - [Electron](https://electronjs.org)
-- [Tauri](https://tauri.app)
 - [Laravel](https://laravel.com)
 - [Symfony](https://symfony.com)
 - [Static PHP CLI](https://github.com/crazywhalecc/static-php-cli/)

resources/views/docs/desktop/1/publishing/building.md

@@ -16,7 +16,7 @@ Before you prepare a distributable build, please make sure you've been through t
 ## Building
 
 The build process compiles your app for one platform at a time. It compiles your application along with the
-Electron/Tauri runtime into a single executable.
+Electron runtime into a single executable.
 
 Once built, you can distribute your app however you prefer, but NativePHP also provides a [publish command](publishing)
 that will automatically upload your build artifacts to your chosen [provider](/docs/publishing/updating) - this allows

resources/views/docs/desktop/1/testing/basics.md

@@ -4,7 +4,7 @@ order: 99
 ---
 # Understanding fake test doubles
 When working with a NativePHP application, you may encounter an elevated level of difficulty when writing tests for your code.
-This is because NativePHP relies on an Electron/Tauri application to be open at all times, listening to HTTP requests. Obviously,
+This is because NativePHP relies on an Electron application to be open at all times, listening to HTTP requests. Obviously,
 emulating this in a test environment can be cumbersome. You will often hit an HTTP error, and this is normal. This is where
 NativePHP's fake test doubles come in.