9
edits
Changes
Imagine us existing for the last 8 years
=== Website ===
=== Website ===
We look after the URY website, revamp or replace it when it gets old (about twice a year), and make sure that other teams are able to keep it full of content.
We look after the URY website and make sure that other teams are able to keep it full of content.
The website is written in Pyramid, which is a '''Python''' web framework. Coincidentally, computer science students at time of writing now learn Python as an introductory programming language. We also have some Web systems written in '''PHP''' and '''Ruby'''.
The main public website is written in Go, and our website runs on the '''Nginx''' web server.
=== Servers ===
=== Servers ===
Each studio has a few computers, typically running '''Windows''', that are used by presenters for playing out sound, connecting to the Internet, and using our Studio Information Service. These have to be maintained, of course, and it's us that rise to the challenge.
Each studio has a few computers, typically running '''Windows''', that are used by presenters for playing out sound, connecting to the Internet, and using our Studio Information Service. These have to be maintained, of course, and it's us that rise to the challenge.
=== Software ===
=== Software ===
[https://ury.org.uk/ceedox/computing:software:in-house:loggerng Ceedox Documentation]
[https://ury.org.uk/ceedox/computing:software:in-house:loggerng Ceedox Documentation]
LoggerNG is our new-for-2013 output logging system. Our Ofcom licence means we have to have a log of 42 days of output at all times - if we aren't recording, we aren't broadcasting. The old logger system runs on some vintage desktop hardware from around 2001, so we needed something new.
LoggerNG is our output logging system. Our Ofcom licence means we have to have a log of 42 days of output at all times - if we aren't recording, we aren't broadcasting. The old logger system runned on some vintage desktop hardware from around 2001, so we needed something new.
LoggerNG includes two dedicated servers, a ''sox''-based recording program, 65 days of FLAC files and a HTML5 download interface on a third server. It's a big thing, and needs to work 100% of the time, all the time (well, term time).
LoggerNG includes two dedicated servers, a ''sox''-based recording program, 65 days of FLAC files and a HTML5 download interface on a third server. It's a big thing, and needs to work 100% of the time, all the time (well, term time).
The server side of the system manages the ability to play out different audio to different sound cards. It lacks lots of functionality, but is in fact very very good at what it does.
The server side of the system manages the ability to play out different audio to different sound cards. It lacks lots of functionality, but is in fact very very good at what it does.
It is a computing team joke about people starting BAPS3. Various people have tried this, and the current try is a server called BAPSicle using the WebStudio interface. Let's see if it works.
==== If No Show, I Do an Instantly Organised, Unending Show - Totally Outrageous Non-stop Entertainment System (insidious Tones (iTones)) ====
==== If No Show, I Do an Instantly Organised, Unending Show - Totally Outrageous Non-stop Entertainment System (insidious Tones (iTones)) ====
[https://ury.org.uk/ceedox/computing:software:in-house:insidioustones Ceedox Documentation]
[https://ury.org.uk/ceedox/computing:software:in-house:insidioustones Ceedox Documentation]
Publically known as URY's Campus Jukebox, this is the system that plays songs when there's not a presenter on air. It's another of our mission critical things as we can't broadcast silence, but it also has lots of neat tricks in the form of a web interface to define a range of pre-defined playlist schedules and some automated playlist generation. Its scheduler is part of the MyRadio framework and integrates with the telnet interface of a little-known thing called Liquidsoap (a Savonet project). Trust us when we say it is very powerful and a lot of fun to play with.
Publically known as URY's Campus Jukebox, this is the system that plays songs when there's not a presenter on air. It's another of our mission critical things as we can't broadcast silence, but it also has lots of neat tricks in the form of a web interface to define a range of pre-defined playlist schedules and some automated playlist generation. Its scheduler is part of the MyRadio framework and integrates with the telnet interface of a little-known thing called Liquidsoap (a Savonet project). Trust us when we say it is very powerful and a lot of fun to play with. There's also a lot of shouting and arguing with it too. Its a range of emotions.
==== MyRadio ====
==== MyRadio ====
Oh, did I mention we're trying to generalise it so other stations can learn what we do under the hood? It's open sourced at [https://github.com/UniversityRadioYork/MyRadio]!
Oh, did I mention we're trying to generalise it so other stations can learn what we do under the hood? It's open sourced at [https://github.com/UniversityRadioYork/MyRadio]!
==== Show Planner ====
==== WebStudio ====
2020 happened. Pandemic happened. WebStudio got made, to allow people to present from home. Written in TypeScript, React and Redux, with the server side in Python.
==== Show Planner (this is pretty much dead now, this is here for the history) ====
[https://ury.org.uk/ceedox/computing:software:in-house:myury:nipsweb Ceedox Documentation]
[https://ury.org.uk/ceedox/computing:software:in-house:myury:nipsweb Ceedox Documentation]
* BAPS, URY's very own custom playout system (Matt Fortune, 20??/??)
* BAPS, URY's very own custom playout system (Matt Fortune, 20??/??)
* The studio clock system (Lloyd Wallis, 2011/12)
* The studio clock system (Lloyd Wallis, 2011/12)
We also spend a lot of time in the studios just tinkering around, and helping engineering team with Outside Broadcasts.
== Prospective members ==
== Prospective members ==
=== What we use ===
=== What we use ===
As Computing Team's goals involve education and development just as much as professionalism and dependability, there is no requirement for prior knowledge. That being said, some knowledge of any of the following would be a great start:
As Computing Team's goals involve education and development just as much as professionalism and dependability, there is no requirement for prior knowledge. We use all of these things, and you'll learn so much more too!
* Administration of Unix-style systems, especially Debian GNU/Linux and FreeBSD
* Administration of Unix-style systems, especially Debian GNU/Linux and FreeBSD
* Administration of Windows client systems, Active Directory and Windows Server
* Administration of Windows client systems, Active Directory and Windows Server
* Python 2, especially Django
* Python
* PHP
* Go
* SQL, especially PostgreSQL
* SQL, especially PostgreSQL
* Network administration (hardware and software)
* Network administration (hardware and software)
* Continuous integration - Jenkins/Hudson, Travis
* Continuous integration - Jenkins/Hudson, Travis
In a rough reverse chronological order.
In a rough reverse chronological order.
* [[Matthew Stratford]]
* [[Connor Sanders]]
* [[Ben Allen]]
* [[Michael Grace]]
* [[Brooke Hatton]]
* [[Brooke Hatton]]
* [[Sophie Kinley]]
* [[Sophie Kinley]]
* [[Computing Updates: Summer 2013]]
* [[Computing Updates: Summer 2013]]
* [[Computing Updates: Easter 2013]]
* [[Computing Updates: Easter 2013]]
* Spring 2021: We're still here, and realising the wiki is very out of date.