Hi
user
Admin Login:
Username:
Password:
Name:
How did we build Spotify?
--client
pygotham
--show
pygotham_2012
--room The_Spotify_Room_Room_6 1049 --force
Next: (none, at end of list)
show more...
Marks
Author(s):
Jon Åslund
Location
The Spotify Room: Room 6
Date
jun Sat 09
Days Raw Files
Start
16:00
First Raw Start
error-in-template
Duration
00:50:00
Offset
None
End
16:50
Last Raw End
Chapters
Total cuts_time
None min.
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
How_did_we_build_Spotify.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
Locked:
clear this to unlock
Locked by:
user/process that locked.
Start:
initially scheduled time from master, adjusted to match reality
Duration:
length in hh:mm:ss
Name:
Video Title (shows in video search results)
Emails:
email(s) of the presenter(s)
Released:
has someone authorised pubication
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
We are quite big now, but as most companies, we started small. This will be a history lesson if how it started, leading up to where we are now, describing many of the services that make up our backend, why we choose Python, what frameworks and tools we use to build our backend services and how to deploy them. We learned a lot. We still are.
Comment:
production notes
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
Veyepar
Video Eyeball Processor and Review