-
-
Notifications
You must be signed in to change notification settings - Fork 136
Capgo CLI
npm i -g capgo/cliAll 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
Example of capacitor.config.json for appId and AppName, the icon is guess in the resources folder
{
"appId": 'ee.forgr.capacitor_go',
"appName": 'Capgo',
"webDir": 'dist',
}
Optionally, you can give:
-
[appId]your app ID the formatcom.test.appis explained here - icon with
-icon /path/to/my/iconto have a custom icon in the list - name with
-name testto 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 ./wwwto send your code to the cloud - channel with
-channel prodto link this version to channel by default, it'sdev - version with
-version 1.0.0to choose the version number, if not provided it use the one in thepackage.json - external zip link with
-externalto use zipped version from external storage, it should be a zip URL in HTTPS
Example of package.json for version
{
"version": "1.0.2"
}
⛔ 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 -
-versionyour app version already sent to the cloud -
-channelthe channel you want to link the version, it doesn't exist it will be created -
-stateset 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