Modified API to allow audio creation. Bumped haystack version that wa…

[nicoechaniz]

can test with:

curl -X POST -u admin:admin -F "name=tracktest" -F "licence=CC-BY-SA-4.0" -F "description=TrackTest" -F "use_type=track" -F "genre=other" -F "instrument=other" -F "tags=[\"untag\", \"otrotag\"]" -F "audio=@/home/user/track.mp3" http://127.0.0.1:8000/api/audio/

[spiccinini]

Great work!

I have tested it. I found the following issues:

• If you use a user that is not superuser then it fails with 403 error (no permissions)
• The correct command is curl -X POST -u admin:admin -F "name=tracktest" -F "licence=CC-BY-SA-4.0" -F "description=TrackTest" -F "use_type=track" -F "genre=other" -F "instrument=other" -F 'tags=["untag", "otrotag"]' -F "audio=@/home/user/track.mp3" http://127.0.0.1:8000/api/audio/ (use simple quotes outside the double quotes of the tags json)

Maybe not an issue:

• The audio is not binded to any project. At the moment we have all the audios in the database related to a project and we forced that the audio must be part of a project.

[spiccinini]

I create this branch with the permissions fix https://github.com/RedPanal/redpanal/tree/audio_creation_api . What do you think?

[nicoechaniz]

It is looking good @spiccinini :)

[nicoechaniz]

regarding the audio being bound to a project or not I guess it is OK it the model accepts to allow the audio to be unbound. It's still related to the user, so it's not "invisible".

[spiccinini]

Great. I will merge this and the other branch :) Probably a good next step could be to create a simple script to upload all the audios from a directory?