aboutsummaryrefslogtreecommitdiffstats
path: root/mediagoblin/submit/lib.py
Commit message (Collapse)AuthorAgeFilesLines
* Tidy up federation code and add tests to cover more of the APIsJessica Tallon2014-08-181-6/+6
|
* Fix #927 - Clean up federation code after Elrond's reviewJessica Tallon2014-07-301-0/+31
| | | | | | | | - Add json_error and use inplace of json_response where appropriate. - Add garbage_collection to config spec file. - Fix bugs in both garbage collection task and test - Handle /api/whoami when no user logged in and a test for such a case. - Validate ID is correct and user has comment privilege to comment.
* Fixed a small error relating to the default value of media_metadatatilly-Q2014-05-141-1/+1
|
* Made it possible to submit media with the metadata providedtilly-Q2014-04-211-1/+3
|
* Making the API make use of the new submit tooling.Christopher Allan Webber2013-11-141-2/+12
| | | | This commit sponsored by Zakkai Kauffman-Rogoff. Thanks! :)
* Breaking out get_upload_file_limits into its own utility.Christopher Allan Webber2013-11-141-2/+18
| | | | This commit sponsored by Mikael Nordfeldth. Thank you!
* A couple more adjustments for unicode'ification of some arguments.Christopher Allan Webber2013-11-141-2/+2
| | | | This commit sponsored by Bruno Girin. Thank you!
* Generic'ifying the submit code to not rely on the werkzeug FileStorage ↵Christopher Allan Webber2013-11-131-2/+2
| | | | | | | | datastructure Important, because that only makes sense for wsgi! :) This commit sponsored by Geoff Lehr. Thank you!
* Docstring for submit_media()Christopher Allan Webber2013-11-131-0/+18
| | | | This commit sponsored by Benjamin Prager. Thank you!
* Refactoring submission utility to make it more generic! Reusable!Christopher Allan Webber2013-11-131-28/+55
| | | | | This commit sponsored by Joar Wandborg. Joar, thanks for the many things you've done for MediaGoblin!
* Starting to split out a submit_media utilityChristopher Allan Webber2013-11-121-0/+82
|
* Merge remote-tracking branch 'refs/remotes/rodney757/reprocessing'Christopher Allan Webber2013-08-211-3/+7
|\ | | | | | | | | | | Conflicts: mediagoblin/processing/task.py mediagoblin/submit/lib.py
| * Fixing normal submission of media (well for images anyway)Christopher Allan Webber2013-08-161-1/+1
| |
| * Updating to the point where we can allllmost run with the new reprocessing codeChristopher Allan Webber2013-08-161-3/+5
| | | | | | | | This commit sponsored by Odin Hørthe Omdal. Thank you!
| * added image reprocessingRodney Ewing2013-08-161-3/+5
| |
* | -update to latest masterRodney Ewing2013-08-191-2/+2
|/ | | | | | - have mg generate task_id remove
* Refactor submit util new_upload_entryElrond2013-05-211-0/+11
| | | | | | This tool creates an initial media entry for a given user. No magic. It just prefills the license with the user's default license and adds the user as uploader.
* mediagoblin/submit/lib.py: fix typoAlon Levy2013-04-231-1/+1
| | | | Signed-off-by: Alon Levy <alon@pobox.com>
* Refactor file field checking.Elrond2013-03-291-0/+11
| | | | | When uploading, the file field needs some checks, it seems. So refactor them into check_file_field and use around.
* Don't pass request into run_process_mediaSebastian Spaeth2013-01-151-4/+8
| | | | | | | | | People(tm) want to start run_process_media from the CLI and might not have a request object handy. So pass in the feed_url into run_process_media rather than the request object and allow the feed url to be empty (resulting in no PuSH notification at all then). Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
* Make PuSHing the Pubhubsubbub server an async task (#436, #585)Sebastian Spaeth2013-01-151-35/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Notifying the PuSH servers had 3 problems.  1) it was done immediately after sending of the processing task to celery. So if celery was run in a separate process we would notify the PuSH servers before the new media was processed/ visible. (#436) 2) Notification code was called in submit/views.py, so submitting via the API never resulted in notifications. (#585) 3) If Notifying the PuSH server failed, we would never retry. The solution was to make the PuSH notification an asynchronous subtask. This way: 1) it will only be called once async processing has finished, 2) it is in the main processing code path, so even API calls will result in notifications, and 3) We retry 3 times in case of failure before giving up. If the server is in a separate process, we will wait 3x 2 minutes before retrying the notification. The only downside is that the celery server needs to have access to the internet to ping the PuSH server. If that is a problem, we need to make the task belong to a special group of celery servers that has access to the internet. As a side effect, I believe I removed the limitation that prevented us from upgrading celery. Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
* prepare_queue_task: Take app not request.Elrond2012-12-261-3/+6
| | | | | | | | | First rename prepare_entry to prepare_queue_task, because this is really more like what this thing does. Thanks to Velmont for noting that we do not need a request in here, but an "app" is good enough. Which means, that this stuff can be called from tool scripts too.
* Processing: Factor out prepare_entry.Elrond2012-12-261-0/+28
| | | | | prepare_entry handles the task_id setup and generating a queue filename and file. it returns the queue file.
* Factor out the actual calling of the processing.Elrond2012-12-261-0/+24
| | | | | | Calling the processing task and handling the exceptions is easy, but has a bunch of caveats, so factor it out into an easy callable function.
* upload refactor: push url handlingElrond2012-12-261-0/+50
Start to refactor our upload handling in main submit and the api. Start factoring out the handling of PuSH url handling.
generated by cgit v1.2.3 (git 2.25.1) at 2025-09-16 07:31:06 +0000