aboutsummaryrefslogtreecommitdiffhomepage
path: root/server/controllers
Commit message (Collapse)AuthorAgeFilesLines
* Share models between server and clientChocobozzz2017-06-173-6/+12
|
* Use typescript standard and lint all filesChocobozzz2017-06-161-3/+3
|
* Create types for model enumsChocobozzz2017-06-161-1/+2
|
* BaseRequestScheduler -> AbstractRequestSchedulerChocobozzz2017-06-161-2/+2
|
* Fix video update testChocobozzz2017-06-121-1/+1
|
* Update webpack stackChocobozzz2017-06-111-1/+0
|
* Type functionsChocobozzz2017-06-1013-72/+82
|
* require -> importChocobozzz2017-06-0515-24/+22
|
* Type modelsChocobozzz2017-05-2511-17/+18
|
* First typescript iterationChocobozzz2017-05-2022-568/+634
|
* Server: split videos controllerChocobozzz2017-05-054-264/+339
|
* Fix unset video language on video updateChocobozzz2017-05-051-6/+6
|
* Server: Fix video propagation with transcoding enabledChocobozzz2017-05-051-0/+3
|
* Format video blacklistChocobozzz2017-04-261-3/+4
|
* Add ability for an administrator to remove any video (#61)Green-Star2017-04-261-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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 ability to register new userChocobozzz2017-04-091-0/+16
|
* Server: add video language attributeChocobozzz2017-04-072-0/+9
|
* Server: Add NSFW in user profileChocobozzz2017-04-031-1/+4
|
* Server: add nsfw attributeChocobozzz2017-03-282-0/+4
|
* Server: add licence video attributeChocobozzz2017-03-272-0/+9
|
* Add video category supportChocobozzz2017-03-222-0/+10
|
* Server: move pod remove to remote pathChocobozzz2017-03-193-26/+44
|
* Better real world testChocobozzz2017-03-191-1/+5
|
* Server: add config endpointChocobozzz2017-03-102-0/+24
|
* Add like/dislike system for videosChocobozzz2017-03-083-7/+209
|
* Server: add views attribute when sending videos to friendsChocobozzz2017-03-041-1/+2
|
* Update bittorrent-tracker and standard to v9Chocobozzz2017-03-033-3/+0
|
* Fix request schedulers statsChocobozzz2017-02-271-9/+28
|
* Server: implement video viewsChocobozzz2017-02-262-5/+106
|
* Server: make a basic "quick and dirty update" for videosChocobozzz2017-02-262-0/+90
| | | | | | | | 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
* Add email to usersChocobozzz2017-02-181-0/+1
|
* Add email to podsChocobozzz2017-02-161-1/+2
|
* Server: assert remoteId and host pair is uniqueChocobozzz2017-01-271-0/+10
|
* Server: error if we add a pod that already existsChocobozzz2017-01-271-1/+1
|
* Adapt requests controller/front to new informationsChocobozzz2017-01-191-1/+2
|
* Server: paths refractoringChocobozzz2017-01-172-2/+3
|
* Server: remote video validators refractoringChocobozzz2017-01-171-5/+1
|
* Server: remote request process refractoringChocobozzz2017-01-171-20/+20
|
* Server: transaction refractoringChocobozzz2017-01-172-82/+48
|
* Server: fix update remote videoChocobozzz2017-01-151-2/+2
|
* Server: create transaction refractoringChocobozzz2017-01-152-37/+19
|
* Server: retryer transaction wrapper refractoringChocobozzz2017-01-152-50/+30
|
* Server: fix update remote video infohashChocobozzz2017-01-121-2/+12
|
* Server: transaction serializable for videosChocobozzz2017-01-112-2/+2
|
* Server: do not break remote videos processing on errorChocobozzz2017-01-111-9/+24
|
* Server: always check commit resultChocobozzz2017-01-112-13/+26
|
* Server: retry video abuse requests tooChocobozzz2017-01-101-12/+56
|
* Server: try to have a better video integrityChocobozzz2017-01-062-46/+124
|
* Server: add video abuse supportChocobozzz2017-01-044-59/+105
|
* Server: move remote routes in their own directoryChocobozzz2016-12-303-9/+23
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 13:25:45 +0000