-
-
Notifications
You must be signed in to change notification settings - Fork 112
Capgo CLI
npm i -g capgo
All command should be run in your app folder with capacitor project inited. See below
Capacitor: Cross-platform native runtime for web apps
capgo add [appId] --apikey=********
💡 All option will be guessed in your config if not provided
Optionally, you can give:
-
[appId]
your app ID the formatcom.test.app
is explained here - icon with
-icon /path/to/my/icon
to have a custom icon in the list - name with
-name test
to have a custom name in the list
capgo upload [appId] --apikey=********
Optionally, you can give:
-
[appId]
is your app ID the format is explained here - icon with
-path ./www
to send your code to the cloud - channel with
-channel prod
to link this version to channel - version with
-version 1.0.0
to choose the version number, if not provided it use the one in the package.json - external zip link with
-external
to use zipped version from external storage, it should be a zip URL in HTTPS
⛔ Version should be greater than “0.0.0”
💡 Don't forget to update the version number each time you send one, or device will don't see the update
capgo set [appId] --apikey=********
Optionally, you can give:
-
[appId]
your app ID the format is explained here -
-version
your app version already sent to the cloud -
-channel
the channel you want to link the version, it doesn't exist it will be created -
-state
set the channel state, can be private or public. To use in your app, channel need to be public.
capgo delete [appId] --apikey=********
Optionally, you can give:
[appId]
your app ID present in the Cloud
To automate your work, I recommend you make GitHub action do the job of pushing to our server
GitHub action example
Don’t forget to configure CI env variable with your API key