Skip to content
Martin DONADIEU edited this page Apr 16, 2022 · 29 revisions

Join Discord Community

Join the Capacitor-updater Discord Server!

Choose between Auto and Manual

In manual mode, all the logic is handled by the JS, that some good and some bad in both scenario.

Auto

Good ✅
  • No logic to handle, all is done for you
  • Auto-revert is handle for you
  • Statistics of updates available
  • Possibility to revert user
  • Channels to share version to your team
  • Define advanced strategies
Bad 🥲
  • Need to use SemVer
  • Can be problematic to use Capgo cloud for big corporate
  • Long to handle if you need on-premise server

Manual

Good ✅
  • Full control of the update logic
  • No need of version server
Bad 🥲
  • If your update fails, you will not be able to revert
  • Long to handle all scenario yourself

Auto-update

Let the plugin handle all for you

Tutorial

update your capacitor apps seamlessly using capacitor updater

Setup all in 5 mins

automatic build and release with GitHub actions

Auto-push your version after each commit with GitHub action

Register

Before using the CLI, you should register here : https://web.capgo.app/register

Documentation

Capgo CLI

Capgo App

Auto-update

Auto-update on premise

Upgrade from version 2 to 3 Beta

Manual update

Build your own logic in JavaScript

Tutorial

Manual demo

Documentation

Capacitor-updater plugin

Roadmap

Roadmap

Our demo app

GitHub - Cap-go/demo-app: demo app with manual and auto mode

Open source

Everything is open source and under the AGPL-3.0 License.

💡 AGPL-3.0 mean if someone modify the code of the project, it’s mandatory to publish it in open-source with same licensing. If you use the code without modification, that doesn’t concern you. See issue below for more details : https://github.com/Cap-go/capacitor-updater/issues/7

NPM package will be migrated in Capgo NPM Organization soon.

GitHub organization

Clone this wiki locally