[FR] Cloud in a Bottle deployment support

Problem

Fusion users cannot currently install the app directly from its repository through Cloud in a Bottle. The platform expects a root cloudinabottle.toml and a source-buildable container target.

Proposed Solution

Would you accept a contribution adding this support? I have a focused implementation that builds the frontend and backend from source, serves Fusion on port 8080, and stores its SQLite database in persistent app data. Existing password and database settings still take precedence.

Alternatives Considered

An external wrapper could provide the manifest, but it would separate deployment updates from Fusion's repository.

Additional Context

The existing Fly.io and Railway options are unchanged.

[andrewlaack]

I should've mentioned, but I am a developer of cloud in a bottle. I plan to make a repo for distributing fusion under our org, how we have done with other apps, a small shim that container the toml file, but wasn't sure if there was interest in having this included in this repo. There are some benefits, like making direct deployments from this repo without having to look it up in our catalog, but we understand if this isn't of interest.

[0x2E]

Hi, thank you for sharing this platform with us. I think it would be better to maintain it in your repo.