You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 1, 2019. It is now read-only.
Currently, all remote instances are defined in a global property file. This file should continue to provide global options, but Hakbot should allow the creation and management of remote instances on a per team basis. This information would be stored in the database rather than in the global property file.
Access control to a teams remote instance would be governed by the API of the team making the request. A team cannot make requests to use another teams remote instance.
The text was updated successfully, but these errors were encountered:
Currently, all remote instances are defined in a global property file. This file should continue to provide global options, but Hakbot should allow the creation and management of remote instances on a per team basis. This information would be stored in the database rather than in the global property file.
Access control to a teams remote instance would be governed by the API of the team making the request. A team cannot make requests to use another teams remote instance.
The text was updated successfully, but these errors were encountered: