T53161 proces feedback sybren, replace angolia with search
T53161 WIP create elasticsearch app / doc / stuff
T53161 elasticsearch can index nodes now. cli command. NOTE config changes!!
T53161 WIP javascript search WIP WIP
T53161 Proof of Concept working
T53161 Proof of Concept working USER search. WIP js.
T53161 start working on elastic..
T53161 proces feedback sybren, replace angolia with search
T53161 WIP create elasticsearch app / doc / stuff
T53161 elasticsearch can index nodes now. cli command. NOTE config changes!!
T53161 WIP javascript search WIP WIP
T53161 Proof of Concept working
T53161 Proof of Concept working USER search. WIP js.
Merge branch 'elastic' of git.blender.org:pillar into elastic
T53161 project user search now also elastic
T53161 simpification tips from sybren.
T53161 javascript search stuff almost complete.
Merge branch 'master' of git.blender.org:pillar into elastic
search is completely working in frontend now
search is completely working in frontend now
Merge branch 'master' into elastic
Added missing ElasticSearch requirements
T52710 search on id works
Merge branch 'elastic' of git.blender.org:pillar into elastic
T52710 pytests work
T53161 all py.test things PASSES
doc
Differential Revision: https://developer.blender.org/D2950
Both 'video-encoder' and 'admin' roles get 'encode-video' capability,
which allows users to upload video that gets encoded & displayed as a
video. For users without this capability videos are handled as regular
downloads.
Added this button in the /u/ user/embed view, so that admins can easily force a re-check from Blender ID without requiring the user themselves to perform any actions.
Instead of performing a call to the Blender Store, call to Blender ID to
get the user's subscription status.
Currently this is performed as a second HTTP call after logging in; in the
future we may want to include the roles in the login response from Blender
ID, so that we can do this in one call instead of two.
Before this, authentication tokens were kept in the database, even when
someone logged out. This is unwanted behaviour, as logging in will create
yet another token anyway there is no reason to keep the token around.
This allows us to remove the require_roles kwarg at some point, ensuring
that it doesn't fall back to assigning to require_cap instead when that
happens. It's also more explicit everywhere, so it's clearer when we check
for roles or caps.
