Automatic
New stable files from an enabled instance's backups folder are queued in the background.
Cloud backup guide
Google Drive is the first available provider. Setup takes a Google Cloud project and a Desktop app OAuth client ID; no client secret is required.
New stable files from an enabled instance's backups folder are queued in the background.
The launcher requests only drive.file, not access to every file in your Drive.
Restores download an archive into the local backups folder and never replace the live world.
Use a project you control, then enable the Google Drive API for that project.
Enable the Google Drive APIAdd an app name and support email. For an External app in Testing, add the Google account you will connect as a test user.
Open Google Auth PlatformUnder Data Access, add the non-sensitive drive.file scope. It limits Industrialis to files the app creates or that you explicitly share with it.
Review Google Drive scopesOpen Clients, choose Create client, select Desktop app, and copy the client ID. You do not need to paste a client secret or configure a redirect URL.
Create an OAuth clientOpen Launcher Settings → Backups, paste the client ID, choose Save ID, then Connect. Finish consent in the browser that opens.
Open Instance Settings → General and turn on Cloud backups. Stable files in that instance's backups folder are uploaded automatically.
If the OAuth app is in Testing, add the account under Google Auth Platform → Audience → Test users.
Google expires authorizations for External apps left in Testing. Move the app to In production for a durable connection.
Confirm that you copied the client ID from an OAuth client whose application type is Desktop app.
Retry Connect and allow local 127.0.0.1 traffic. The launcher briefly opens a random loopback port to receive Google's response.
Planned providers
S3-compatible storage, OneDrive, FTP/FTPS, and SFTP will use the same snapshot format and backup workflow. Their connection guides will be published when each provider is available.