Repo adapters

A repo adapter is the set of changes a Flagship server makes so an open-source app runs on Flagship: a flagship.app.json manifest, plus any small edits the app needs. The original repo is never changed.

Shared, and public

When a Flagship server's AI adapts a public open-source repo, the server shares the adaptation by default, so the next person can install that repo without needing AI. The server's owner can switch sharing off on the import screen. We publish every adaptation at github.com/ibisllc/flagship-adapters, so anyone can see exactly what Flagship servers will apply, and every server gets the same files.

• We never record who sent one. No account, server or address is attached.
• We publish them in daily batches, dated to the day.
• We only keep adaptations of public repos under an open-source license, and we check them first.
• Each adaptation is under the license of the repo it adapts.
• When we refuse one for a reason it can fix, the server's own AI may fix it and send it again.

Search the directory

Every adaptation that is currently published, by project: where it lives, its license, the digest of each adapter, the upstream commit it was made against and an honest status (published, or disputed when more installs failed than were confirmed). It is the file directory.json in the public repository. There are no install counts and nothing about who sent or installed one, and a status is a record, not a safety claim. Maintainers can make an adaptation unnecessary by committing their own flagship.app.json.

• Loading the directory…

When an adaptation breaks

If an adaptation fails to build or start during an install, the server tells us which adaptation it was and whether it failed to build or to start. Nothing else is sent. A server's owner can also report a problem from the service page, with a short note. We keep notes privately, never publish them, use them only to review the adaptation, and delete them within 90 days, or 180 days after we retire the adaptation so we can learn what went wrong. Please don't put anything in a note that identifies you.

When 3 problems are reported for an adaptation, we retire it, and the next server's AI makes a new one.

The details are in our privacy policy.

Control how your repo runs on Flagship

Commit a flagship.app.json at the root of your repo. Every Flagship server uses it instead of adapting the repo itself, and we never keep or share adaptations of a repo that has one, so committing one also takes your repo out of our index.

To make one, write it by hand (see Apps & manifest), or import your repo on your own Flagship server, check it runs, then use Get flagship.app.json on the import screen and commit the file it gives you.

For repo owners

If you don't want us to keep adaptations of your repo, email legal@flagshipserver.com from an address that shows you control the repo, or open an issue on it that we can verify. We'll add it to do-not-adapt.txt in the public index, which removes its adaptations at the next daily publish, and Flagship servers stop using them. Git history keeps earlier versions.

We can't stop someone running open-source code on their own server, so people can still adapt your repo there. We just won't keep or share it.