-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AppAPI 2.0 Release Information #213
Comments
See: nextcloud/app_api#213 1. _All Talk Bots should be updated to use AppAPI auth for input endpoints._ 2. Updated Documentation reflecting last changes. 3. CI will fail, until merge in AppAPI will finished. --------- Signed-off-by: Alexander Piskun <bigcat88@icloud.com>
This is not possible in AIO. Cannot you take care of this during the upgrade of the app? |
What happens if you dont do this and simply update the app? |
IMHO: in AIO, in theory, everything should be fine with the deployment daemon, since AIO Docker Socket Proxy did not changed. Related to ExApps: there were no so much of them, and the changes were only to TalkBots API. |
All right, thanks! I guess we dont need to adjust things in AIO then. |
We are preparing with joy and optimism for the release of AppAPI version 2.0
Ref: #212
The main innovations of this version for Administrators:
The main cool difference for the developers:
protocol
ininfo.xml
is deprecated and ignored from now. All ExApps should implement only simple HTTP.occ app_api:app:register appName manual_install --json-info
- does not requireprotocol
orhost
fields anymore, these values are from now calculated based on Daemon values.exAppRequest
orexAppRequestWithUserInit
from PublicFunctions.php, as it handles new Auth correctly for Docker Socket Proxy installs.How to Update from 1.x version to 2.0 version?
Ideal variant is:
Variant when you first got update to AppAPI 2.0 and after that found this topic:
oc_ex_apps
,oc_ex_apps_daemons
,oc_appconfig_ex
,oc_preferences_ex
tables.oc_talk_bots_conversation
,oc_talk_bots_server
tables.redis-cli
andflushAll
after that inside redis command line)Feel free to ask questions inside this topic if something is unclear.
The text was updated successfully, but these errors were encountered: