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
This build currently contains a local database. We must remove any of the following that relate to localdb (reasondb)
Modules
Packages
Documentation
Notes from previous build:
API’s Currently added through the interface and stored in localdb. Could be part of config? For now, that seems like a good idea. Why would anyone else apart from engineers add and remove APIs anyway?
Users Currently stored locally, but could come directly from API collection, for now, until we decide how API users can look
Collections Previously we needed to cache these to deliver on each page load, but I see no reason why we don’t just have the frontend request these on load. The collection endpoint is fast to resolve and with this being a webapp there would be a single request per session. We could memcache them on the server. Thats also lightweight.
Workers Interval tasks are no longer part of Publish
ACL Roles are not part of the new Publish, yet. That again is something that we could handle directly in API after we scope
The text was updated successfully, but these errors were encountered:
This build currently contains a local database. We must remove any of the following that relate to localdb (reasondb)
Notes from previous build:
The text was updated successfully, but these errors were encountered: