aboutsummaryrefslogtreecommitdiffhomepage
path: root/server/models
Commit message (Collapse)AuthorAgeFilesLines
* Reorganize model filesChocobozzz2017-06-1642-68/+75
|
* Convert scripts to typescriptChocobozzz2017-06-121-1/+1
|
* Better models define typingChocobozzz2017-06-1117-31/+31
|
* Use shared modelsChocobozzz2017-06-112-3/+3
|
* Type functionsChocobozzz2017-06-1033-216/+429
|
* require -> importChocobozzz2017-06-051-6/+6
|
* Type modelsChocobozzz2017-05-2536-543/+1359
|
* First typescript iterationChocobozzz2017-05-2018-178/+155
|
* Server: finish old jobs at startupChocobozzz2017-05-051-2/+2
|
* Server: add job scheduler to transcode video filesChocobozzz2017-05-042-22/+148
|
* Server: little refractoring when listing videosChocobozzz2017-05-011-10/+12
|
* Format video blacklistChocobozzz2017-04-261-1/+0
|
* Add ability for an administrator to remove any video (#61)Green-Star2017-04-263-11/+134
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add ability for an admin to remove every video on the pod. * Server: add BlacklistedVideos relation. * Server: Insert in BlacklistedVideos relation upon deletion of a video. * Server: Modify BlacklistedVideos schema to add Pod id information. * Server: Moving insertion of a blacklisted video from the `afterDestroy` hook into the process of deletion of a video. To avoid inserting a video when it is removed on its origin pod. When a video is removed on its origin pod, the `afterDestroy` hook is fire, but no request is made on the delete('/:videoId') interface. Hence, we insert into `BlacklistedVideos` only on request on delete('/:videoId') (if requirements for insertion are met). * Server: Add removeVideoFromBlacklist hook on deletion of a video. We are going to proceed in another way :). We will add a new route : /:videoId/blacklist to blacklist a video. We do not blacklist a video upon its deletion now (to distinguish a video blacklist from a regular video delete) When we blacklist a video, the video remains in the DB, so we don't have any concern about its update. It just doesn't appear in the video list. When we remove a video, we then have to remove it from the blacklist too. We could also remove a video from the blacklist to 'unremove' it and make it appear again in the video list (will be another feature). * Server: Add handler for new route post(/:videoId/blacklist) * Client: Add isBlacklistable method * Client: Update isRemovableBy method. * Client: Move 'Delete video' feature from the video-list to the video-watch module. * Server: Exclude blacklisted videos from the video list * Server: Use findAll() in BlacklistedVideos.list() method * Server: Fix addVideoToBlacklist function. * Client: Add blacklist feature. * Server: Use JavaScript Standard Style. * Server: In checkUserCanDeleteVideo, move the callback call inside the db callback function * Server: Modify BlacklistVideo relation * Server: Modifiy Videos methods. * Server: Add checkVideoIsBlacklistable method * Server: Rewrite addVideoToBlacklist method * Server: Fix checkVideoIsBlacklistable method * Server: Add return to addVideoToBlacklist method
* Server: add video language attributeChocobozzz2017-04-071-0/+19
|
* Server: Add NSFW in user profileChocobozzz2017-04-031-0/+12
|
* Server: add nsfw attributeChocobozzz2017-03-281-0/+13
|
* Server: add licence video attributeChocobozzz2017-03-271-0/+18
|
* Add video category supportChocobozzz2017-03-221-0/+18
|
* Add like/dislike system for videosChocobozzz2017-03-083-2/+109
|
* Server: add views attribute when sending videos to friendsChocobozzz2017-03-041-2/+4
|
* Server: fix migrations with an empty Applications tableChocobozzz2017-03-041-1/+1
|
* Server: implement video viewsChocobozzz2017-02-264-6/+179
|
* Server: make a basic "quick and dirty update" for videosChocobozzz2017-02-265-65/+232
| | | | | | | | This system will be useful to to update some int video attributes (likes, dislikes, views...) The classic system is not used because we need some optimization for scaling
* Server: fix migration scriptsChocobozzz2017-02-181-1/+1
|
* Server: use a request scheduler object instance for friendsChocobozzz2017-02-181-181/+27
| | | | communication
* Add email to usersChocobozzz2017-02-183-3/+31
|
* Server: add unique to unique indexesChocobozzz2017-02-163-3/+10
|
* Add email to podsChocobozzz2017-02-161-0/+5
|
* Fix update host scriptChocobozzz2017-02-081-1/+1
|
* Client: add basic support to report video abusesChocobozzz2017-01-231-1/+2
|
* Server: paths refractoringChocobozzz2017-01-171-13/+18
|
* Server: requests refractoringChocobozzz2017-01-171-38/+38
|
* Server: fix single pod testsChocobozzz2017-01-121-1/+1
|
* Server: fix update remote video infohashChocobozzz2017-01-121-1/+2
|
* Server: transaction serializable for videosChocobozzz2017-01-111-1/+1
|
* Server: do not break remote videos processing on errorChocobozzz2017-01-111-2/+2
|
* Server: improve requests schedulerChocobozzz2017-01-102-42/+105
|
* Server: try to have a better video integrityChocobozzz2017-01-062-3/+10
|
* Server: use crypto instead of ursa for pod signatureChocobozzz2017-01-041-1/+1
|
* Server: we don't need the video name when removing a remote videoChocobozzz2017-01-041-1/+0
|
* Server: add video abuse supportChocobozzz2017-01-044-0/+121
|
* Server: add updatedAt attribute to videosChocobozzz2016-12-301-2/+4
|
* Server: propagate video update to other podsChocobozzz2016-12-301-3/+3
|
* Server: add ability to update a videoChocobozzz2016-12-291-2/+19
|
* Server: little refractoringChocobozzz2016-12-292-2/+67
|
* Server: use binary data instead of base64 to send thumbnailsChocobozzz2016-12-291-5/+6
|
* Server: use video hook to send information to other pods when a video isChocobozzz2016-12-291-0/+14
| | | | deleted
* Server: add association between author and userChocobozzz2016-12-293-3/+19
|
* Server: Add postgresql indexesChocobozzz2016-12-299-13/+104
|
* Server: add database field validationsChocobozzz2016-12-289-61/+147
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-14 17:14:17 +0000