Starchive Wiki - User contributions [en-gb]

Broadcasting via Discord

2020-09-22T11:37:57Z

Kieran: changed music bot information to use new bot (rythm)

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Notes about the video:'''
* You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.
* We've had to change our music bot so some of the commands have changed - don't worry, we'll go through everything during training and the <code>#broadcasting-guide</code> channel and this wiki have been updated with the commands for the new music bot.

== Getting Started ==
# [https://discord.gg/vfEH3dx Join the Discord server].
# Verify yourself with our Discord system. Only current show hosts can have shows on our remote broadcasting system. In order to verify youself, use the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you signed up with when you applied to be a show host. Normally, this is your University email address. Type the command in the <code>#registration</code> channel and the the bot will give you the role you need to host shows.
# Read the rest of this guide so you know how the system works.

== Server Channels ==
A channel is like a chat room, and a server is a group of channels.

Our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

Voice channels are for audio only, and chat channels are for text messages only. So, to control access to <code>#the-studio</code> and to control the music bot, send your command messages into <code>#control-room</code>. Any non-command messages in <code>#control-room</code> are ignored by our bots, so you can also use this text channel to talk to your co-presenters during your show.

== Going Live ==
At the time of your show, you and your co-hosts will automatically be given access to the studio. You can't access any of the broadcast channels until your show time.

To get started on air:
# Connect to <code>#the-studio</code> voice channel.
# Open the <code>#control-room</code> text channel.

Commands to control the music bot should all be sent in <code>#control-room</code>. You can also message your co-hosts there.

Everything in <code>#the-studio</code> is sent to broadcast, including your mic and music. You can use the mute button to turn off your microphone if you don't want your voice going to air (for example, during a song).

Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. If there's already music playing when you came in, or you arrived a bit late to the studio, these commands might help you out:
* <code>_clear</code>: This will remove every song from the music queue. When the currently playing song has finished, no more songs will be played, which is a good time for you to get on air!
* <code>_nowplaying</code>: When you begin your show, you might want to let people know whatever song was just playing. If so, this command will show whatever song is currently playing.

At your show's end time, you will all be automatically removed from the studio.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Plays the music player.
* <code>_play <YouTube link></code> (without angle brackets): Queues the specified YouTube link for playout.
* <code>_play <search term></code> (without angle brackets): Searches YouTube for the specified term, then queues the first result.
* <code>_pause</code>: Pause or resume the music player.
* <code>_leave</code>: Stops the music player completely. This will also clear the queue and remove the music bot from the studio.
* <code>_skip</code>: Skip the current track in the queue and start playing what's next.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Shows what's currently playing.
* <code>_queue</code>: Shows the music that's currently queued.

You can see all music commands by heading to [https://rythmbot.co/features#list Rythm's help page] or by sending <code>_help</code> to <code>#control-room</code>.

=== Other Commands ===
* <code>!listeners</code>: This will let you know how many people are currently tuned in to STAR.
* <code>!invite</code> and <code>!uninvite</code>: If you have a guest on your show, you can ask them to join the Discord server using the link above, then you can use the command <code>!invite @guest-username</code> to give them access to the studio. Your guests don't need to go through the <code>!verify</code> process. To remove someone, use <code>!uninvite @guest-username</code>. Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.
* <code>!addhost</code> and <code>!removehost</code>: If you have a new co-host, you can use <code>!addhost @host-username</code> to automatically give them access to the studio during your show each week. To stop granting someone access, use <code>!removehost @host-username</code>. If you've got a guest who only needs access once, use <code>!invite</code> (above) instead. Again, be careful not to remove yourself by accident and get locked out of the studio!

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://rythmbot.co/ Rythm], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

Broadcasting via Discord

2020-09-21T19:24:06Z

Kieran: changed verification process to no longer dm

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home.

If you prefer, you can [https://www.youtube.com/watch?v=Pj_unlpNoeI watch our tutorial video on YouTube] that guides you through the process of getting and running your show. This wiki page is likely the definitive guide, though.

'''Note about the video:''' You don't need to ask in <code>#registration</code> for someone to register your show - that'll be done automatically after your practice slot. You do still need to verify yourself with <code>!verify</code>, though.

== Getting Started ==
# [https://discord.gg/vfEH3dx Join the Discord server].
# Verify yourself with our Discord system. Only current show hosts can have shows on our remote broadcasting system. In order to verify youself, use the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you signed up with when you applied to be a show host. Normally, this is your University email address. Type the command in the <code>#registration</code> channel and the the bot will give you the role you need to host shows.
# Read the rest of this guide so you know how the system works.

== Server Channels ==
A channel is like a chat room, and a server is a group of channels.

Our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

Voice channels are for audio only, and chat channels are for text messages only. So, to control access to <code>#the-studio</code> and to control the music bot, send your command messages into <code>#control-room</code>. Any non-command messages in <code>#control-room</code> are ignored by our bots, so you can also use this text channel to talk to your co-presenters during your show.

== Going Live ==
At the time of your show, you and your co-hosts will automatically be given access to the studio. You can't access any of the broadcast channels until your show time.

To get started on air:
# Connect to <code>#the-studio</code> voice channel.
# Open the <code>#control-room</code> text channel.

Commands to control the music bot should all be sent in <code>#control-room</code>. You can also message your co-hosts there.

Everything in <code>#the-studio</code> is sent to broadcast, including your mic and music. You can use the mute button to turn off your microphone if you don't want your voice going to air (for example, during a song).

Every hour, Gorilla Joe will enter the studio and play some music if nobody is present. If there's already music playing when you came in, or you arrived a bit late to the studio, these commands might help you out:
* <code>_remove all</code>: This will remove every song from the music queue. When the currently playing song has finished, no more songs will be played, which is a good time for you to get on air!
* <code>_nowplaying</code>: When you begin your show, you might want to let people know whatever song was just playing. If so, this command will show whatever song is currently playing.

At your show's end time, you will all be automatically removed from the studio.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Plays the music player.
* <code>_play <YouTube link></code> (without angle brackets): Queues the specified YouTube link for playout.
* <code>_play <search term></code> (without angle brackets): Searches YouTube for the specified term, then queues the first result.
* <code>_pause</code>: Pause or resume the music player.
* <code>_stop</code>: Stop the music player.
* <code>_skip</code>: Skip the current track in the queue and start playing what's next.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the queue.
* <code>_nowplaying</code>: Shows what's currently playing.
* <code>_queue</code>: Shows the music that's currently queued.

You can see all music commands by sending <code>_help</code> to <code>#control-room</code>, but be aware the list it sends back doesn’t include the leading underscore before each command.

=== Other Commands ===
* <code>!listeners</code>: This will let you know how many people are currently tuned in to STAR.
* <code>!invite</code> and <code>!uninvite</code>: If you have a guest on your show, you can ask them to join the Discord server using the link above, then you can use the command <code>!invite @guest-username</code> to give them access to the studio. Your guests don't need to go through the <code>!verify</code> process. To remove someone, use <code>!uninvite @guest-username</code>. Be careful - if you accidentally uninvite yourself and get locked out of the studio, there might not someone available to let you back in.
* <code>!addhost</code> and <code>!removehost</code>: If you have a new co-host, you can use <code>!addhost @host-username</code> to automatically give them access to the studio during your show each week. To stop granting someone access, use <code>!removehost @host-username</code>. If you've got a guest who only needs access once, use <code>!invite</code> (above) instead. Again, be careful not to remove yourself by accident and get locked out of the studio!

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://octave.gg Octave], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

Broadcasting via Discord

2020-08-28T13:49:49Z

Kieran: added youtube link

To allow shows to continue during the [https://en.wikipedia.org/wiki/2019–20_coronavirus_pandemic Coronavirus pandemic], a Discord server has been set up. The server allows shows to broadcast from home. Although this guide is probably the most definitive source of information, we also created a YouTube video that guides you through the process of getting and running your show. You can view the video by [https://www.youtube.com/watch?v=Pj_unlpNoeI clicking here].

== Getting Started ==
# [https://discord.gg/vfEH3dx Join the Discord server].
# Verify yourself with our Discord system. Only current show hosts can have shows on our remote broadcasting system. In order to verify youself, use the command <code>!verify <email address></code>, where <code><email address></code> (without angle brackets) is the email address you signed up with when you applied to be a show host. Normally, this is your university email address. Send the command in a private message to the Gorilla Joe bot (<code>Starbot Admin#9915</code>) - look for the list of server members to find the bot. Then, follow the instructions you receive back.
# Head into the <code>#registration</code> channel and let us know what time slot you'd like, and what you'd like your show to be called. You can see what times are available on the schedule in the <code>#schedule</code> channel.
# Read the rest of this guide so you know how the system works.

== Server Channels ==
A channel is like a chat room, and a server is a group of channels.

Our text chat channels are:
* <code>#info</code>: guidance and help.
* <code>#just-chatting</code>: general chit chat.
* <code>#help-me</code>: for technical help during your show. Mention <code>@Tech Team</code> in your message!
* <code>#broadcasting-guide</code>: guidance for going live.
* <code>#control-room</code>: chatting with co-presenters during your show, and controlling the music bot.

Our voice channels are:
* <code>#the-studio</code>: audio in this channel will go live on air. This is where the music bot plays music, and where you and your co-presenters should talk to broadcast.

Voice channels are for audio only, and chat channels are for text messages only. So, to control access to <code>#the-studio</code> and to control the music bot, send your command messages into <code>#control-room</code>. Any non-command messages in <code>#control-room</code> are ignored by our bots, so you can also use this text channel to talk to your co-presenters during your show.

== Going Live ==
At the time of your show, one of your presenters (probably whoever posted in <code>#registration</code>) will be given access to the studio. You can't access any of the broadcast channels until your show time.

Once you're in, send <code>!invite @co-presenter-username</code> into <code>#control-room</code> to give your co-presenters access. To remove someone, use <code>!uninvite @co-presenter-username</code>. Be careful! If you kick yourself out and get locked out of the studio, there might not always be someone available to let you back in immediately.

Commands to control the music bot and invite your co-presenters to the studio should all be sent in <code>#control-room</code>. Make sure you're connected to <code>#the-studio</code> voice channel. You can then listen to what's happening on STAR by "undeafening" yourself, and turn your mic on or off with the mute button.

Every hour Gorilla Joe will enter the studio and play some music if nobody is present. If there's already music playing when you came in, or you arrived a bit late to the studio, these commands might help you out:
* <code>_remove all</code>: This will remove every song that is currently playing from the queue. When the currently playing song has finished, no more songs will be played which is a good time for you to get on air!
* <code>_nowplaying</code>: When you begin your show, you might want to let people know whatever song was just playing. If so, this command will show whatever song is currently playing and will also give you a link to the source of the song if you fancy sharing it.

At your show's end time, you will all be automatically removed from the studio.

=== Controlling Music ===
The music is controlled by sending commands to the <code>#control-room</code> channel. Different commands take different parameters (bits of extra info) after them - the music bot will tell you what to add if you don't provide it first time.

All music commands start with <code>_</code>.

Some key commands are:
* <code>_play</code>: Plays the music player.
* <code>_play <YouTube link></code> (without angle brackets): Queues the specified YouTube link for playout.
* <code>_pause</code>: Pause or resume the music player.
* <code>_stop</code>: Stop and clear the music player.
* <code>_skip</code>: Skip the current music track.
* <code>_remove</code>: Remove a song from the queue.
* <code>_shuffle</code>: Shuffle the music queue.
* <code>_nowplaying</code>: Shows what's currently playing.
* <code>_queue</code>: Shows the music that's currently queued.
* <code>_volume</code>: Set the volume of the music player.
* <code>_youtube</code>: Search and see YouTube results.
* <code>_soundcloud</code>: Search and see SoundCloud results.

You can see all music commands by sending <code>_help</code> to <code>#control-room</code>, but be aware the list it sends back doesn’t include the leading underscore before each command.

== Get Help ==
If you need help, message the <code>#help-me</code> channel in Discord and mention <code>@Tech Team</code> to send a notification to the tech team.

You can also email [mailto:tech@standrewsradio.com?subject=Discord%20Broadcasting%20Help tech@standrewsradio.com].

== Technical Implementation ==
''This section is intended for STAR Tech Team's reference.''

The Discord server is powered by:
* [https://github.com/StAndrewsRadio/starbot-admin starbot-admin], a custom-developed bot for managing the station in Discord.
* [https://github.com/StAndrewsRadio/starbot-forwarder starbot-forwarder], a custom-developed bot to send a Discord voice channel to our streaming server.
* [https://octave.gg Octave], for music.
* [https://carl.gg Carl], for announcements, logging, etc.

Stream Status

2020-02-22T00:05:00Z

Kieran: updated script

The Stream Status tool is comprised of a command that checks for stream silence and a PHP page that reports this for the uptime monitor. The script is hosted at [https://standrewsradio.com/stream-status.php standrewsradio.com/stream-status.php].

== Command ==
The command is as follows:
<syntaxhighlight lang="bash">
ffmpeg -i http://garfield.standrewsradio.com:8080/stream/1.mp3 -y -nostats -loglevel 0 -f mp3 -t 00:00.5 - | sox -t mp3 - -n stat 2>&1 | grep "Maximum amplitude" | cut -d' ' -f 7
</syntaxhighlight>

This is split into four different parts, each operating on the output of the part before:

# <syntaxhighlight lang="bash" inline>ffmpeg -i http://garfield.standrewsradio.com:8080/stream/1.mp3 -y -nostats -loglevel 0 -f mp3 -t 00:00.5 -</syntaxhighlight>: silently records half a second of the stream as an mp3.
# <syntaxhighlight lang="bash" inline>sox -t mp3 - -n stat 2>&1</syntaxhighlight>: using sox, read the MP3 recording and get some statistics on it, piping stderr and stdout into stdout.
# <syntaxhighlight lang="bash" inline>grep "Maximum amplitude"</syntaxhighlight>: gets the line of the output that contains information about the maximum amplitude.
# <syntaxhighlight lang="bash" inline>cut -d' ' -f 7</syntaxhighlight>: cuts the input into parts around spaces and returns the 7th part (this is the maximum amplitude in seconds).

== PHP ==
The PHP script is as follows:
<syntaxhighlight lang="php">
<?php

$output = exec("<the command>");
$val = floatval($output);

if ($val < 0.00025) {
http_response_code(503);
} else {
echo "all good :) max amplitude was $val!";
http_response_code(200);
}
</syntaxhighlight>

This script simply gets the output of the command that is run and checks the value. If it less than 0.00025, it returns a server error response code for the uptime robot to detect. This number has been chosen completely arbitrarily based on the fact that "silence" appears to fluctuate between 0.0001 and 0.0002.

Stream Status

2020-02-21T23:42:47Z

Kieran:

The Stream Status tool is comprised of a command that checks for stream silence and a PHP page that reports this for the uptime monitor. The script is hosted at [https://standrewsradio.com/stream-status.php standrewsradio.com/stream-status.php].

== Command ==
The command is as follows:
<syntaxhighlight lang="bash">
ffmpeg -i http://garfield.standrewsradio.com:8080/stream/1.mp3 -y -nostats -loglevel 0 -f mp3 -t 00:00.5 - | sox -t mp3 - -n stat 2>&1 | grep "Maximum amplitude" | cut -d' ' -f 7
</syntaxhighlight>

This is split into four different parts, each operating on the output of the part before:

# <syntaxhighlight lang="bash" inline>ffmpeg -i http://garfield.standrewsradio.com:8080/stream/1.mp3 -y -nostats -loglevel 0 -f mp3 -t 00:00.5 -</syntaxhighlight>: silently records half a second of the stream as an mp3.
# <syntaxhighlight lang="bash" inline>sox -t mp3 - -n stat 2>&1</syntaxhighlight>: using sox, read the MP3 recording and get some statistics on it, piping stderr and stdout into stdout.
# <syntaxhighlight lang="bash" inline>grep "Maximum amplitude"</syntaxhighlight>: gets the line of the output that contains information about the maximum amplitude.
# <syntaxhighlight lang="bash" inline>cut -d' ' -f 7</syntaxhighlight>: cuts the input into parts around spaces and returns the 7th part (this is the maximum amplitude in seconds).

== PHP ==
The PHP script is as follows:
<syntaxhighlight lang="php">
<?php
$output = exec("<the command>");
$val = floatval($output);

if ($val === 0.0) {
http_response_code(503);
} else {
echo "all good :)";
http_response_code(200);
}
</syntaxhighlight>

This script simply gets the output of the command that is run and checks the value. If it is 0, it returns a server error response code for the uptime robot to detect.

Stream Status

2020-02-21T23:41:37Z

Kieran: /* Stream Status */

The Stream Status tool is comprised of a command that checks for stream silence and a PHP page that reports this for the uptime monitor.

== Command ==
The command is as follows:
<syntaxhighlight lang="bash">
ffmpeg -i http://garfield.standrewsradio.com:8080/stream/1.mp3 -y -nostats -loglevel 0 -f mp3 -t 00:00.5 - | sox -t mp3 - -n stat 2>&1 | grep "Maximum amplitude" | cut -d' ' -f 7
</syntaxhighlight>

This is split into four different parts, each operating on the output of the part before:

# <syntaxhighlight lang="bash" inline>ffmpeg -i http://garfield.standrewsradio.com:8080/stream/1.mp3 -y -nostats -loglevel 0 -f mp3 -t 00:00.5 -</syntaxhighlight>: silently records half a second of the stream as an mp3.
# <syntaxhighlight lang="bash" inline>sox -t mp3 - -n stat 2>&1</syntaxhighlight>: using sox, read the MP3 recording and get some statistics on it, piping stderr and stdout into stdout.
# <syntaxhighlight lang="bash" inline>grep "Maximum amplitude"</syntaxhighlight>: gets the line of the output that contains information about the maximum amplitude.
# <syntaxhighlight lang="bash" inline>cut -d' ' -f 7</syntaxhighlight>: cuts the input into parts around spaces and returns the 7th part (this is the maximum amplitude in seconds).

== PHP ==
The PHP script is as follows:
<syntaxhighlight lang="php">
<?php
$output = exec("<the command>");
$val = floatval($output);

if ($val === 0.0) {
http_response_code(503);
} else {
echo "all good :)";
http_response_code(200);
}
</syntaxhighlight>

This script simply gets the output of the command that is run and checks the value. If it is 0, it returns a server error response code for the uptime robot to detect.

Stream Status

2020-02-21T23:40:50Z

Kieran: Created page with "= Stream Status = The Stream Status tool is comprised of a command that checks for stream silence and a PHP page that reports this for the uptime monitor. == Command == The c..."

= Stream Status =
The Stream Status tool is comprised of a command that checks for stream silence and a PHP page that reports this for the uptime monitor.

== Command ==
The command is as follows:
<syntaxhighlight lang="bash">
ffmpeg -i http://garfield.standrewsradio.com:8080/stream/1.mp3 -y -nostats -loglevel 0 -f mp3 -t 00:00.05 - | sox -t mp3 - -n stat 2>&1 | grep "Maximum amplitude" | cut -d' ' -f 7
</syntaxhighlight>

This is split into four different parts, each operating on the output of the part before:

# <syntaxhighlight lang="bash" inline>ffmpeg -i http://garfield.standrewsradio.com:8080/stream/1.mp3 -y -nostats -loglevel 0 -f mp3 -t 00:00.5 -</syntaxhighlight>: silently records half a second of the stream as an mp3.
# <syntaxhighlight lang="bash" inline>sox -t mp3 - -n stat 2>&1</syntaxhighlight>: using sox, read the MP3 recording and get some statistics on it, piping stderr and stdout into stdout.
# <syntaxhighlight lang="bash" inline>grep "Maximum amplitude"</syntaxhighlight>: gets the line of the output that contains information about the maximum amplitude.
# <syntaxhighlight lang="bash" inline>cut -d' ' -f 7</syntaxhighlight>: cuts the input into parts around spaces and returns the 7th part (this is the maximum amplitude in seconds).

== PHP ==
The PHP script is as follows:
<syntaxhighlight lang="php">
<?php
$output = exec("<the command>");
$val = floatval($output);

if ($val === 0.0) {
http_response_code(503);
} else {
echo "all good :)";
http_response_code(200);
}
</syntaxhighlight>

This script simply gets the output of the command that is run and checks the value. If it is 0, it returns a server error response code for the uptime robot to detect.

Tech Info

2020-02-21T23:23:31Z

Kieran: correct formatting errors

Information on this page is intended for the Tech Team.

== Email Accounts ==
* STAR's emails are managed via [https://admin.google.com/standrewsradio.com admin.google.com/standrewsradio.com]
* STAR has a G Suite legacy account (i.e. created before December 2012), allowing the creation of unlimited free accounts, each with 15GB of storage.
** We started using G Suite around May 2008 (citation needed)
* Email addresses for committee members should follow forename.surname@standrewsradio.com.
* There are also multiple groups, e.g. news@, music@, programming@, and hello@. Committee members can be added to groups to receive emails sent to the group. Emails cannot be sent from a group address.
* Both users and groups may have aliases, e.g. bo@ redirects to manager@.
* The invalid user account, *@, will catch any emails sent to non-existent addresses within our domain. This is useful for unlocking old STAR pages connected to long-departed committee members.

== Stream URLs ==
* MP3: [https://garfield.standrewsradio.com:8081/stream/1.mp3 garfield.standrewsradio.com:8081/stream/1.mp3]
* Ogg: [https://garfield.standrewsradio.com:8081/stream/1.ogg garfield.standrewsradio.com:8081/stream/1.ogg]

== Domains ==
* STAR also owns [http://standrewsradio.co.uk standrewsradio.co.uk]; it should simply redirect to the main site.
* Domains are managed by Rachel Hughes, Union Design & Marketing Manager ([mailto:sadesign@st-andrews.ac.uk sadesign@st-andrews.ac.uk])
* The rapid.standrewsradio.com subdomain was associated with RapidSwitch; STAR moved from RapidSwitch to DigitalOcean in 2019, so no rapid. URLs should now be in use.

== Subdomains ==
* [https://studio.standrewsradio.com studio.standrewsradio.com]: the version of the Buzzbox displayed in the studio, showing listener counter and help section.
* [https://listen.standrewsradio.com listen.standrewsradio.com]: a separate version of the Buzzbox.
* [https://buzzbox.standrewsradio.com/ buzzbox.standrewsradio.com]: the listen. subdomain without the STAR logo at the top.
* [https://help.standrewsradio.com/ help.standrewsradio.com]: contains the help section, which is also shown within the studio. subdomain.
* [http://archive.standrewsradio.com/ archive.standrewsradio.com]: you are here.
* [https://status.standrewsradio.com/ status.standrewsradio.com]: website status (subdomain created 5th Feb 2020).
* [https://manage.standrewsradio.com/ manage.standrewsradio.com]: .svg version of 2012 Gorilla Joe logo.
** [https://manage.standrewsradio.com/grafana manage.standrewsradio.com/grafana]: graph of listener stats (Grafana removed 5th Feb 2020 due to unreliability and a planned move to Google Analytics).
** [http://manage.standrewsradio.com/icecast manage.standrewsradio.com/icecast]: global server stats, and list of mount points.
** [https://manage.standrewsradio.com/netdata manage.standrewsradio.com/netdata]: extensive server stats.

== Tools ==
* [[Podcast Recorder]]: shell script that records, stores and cleans up archived podcasts.
* [https://github.com/Kezz101/ic2ga ic2ga]: Java programme that forwards Icecast statistics to Google Analytics.
* [[Stream Status]]: PHP page that checks if the stream is currently silent.

== Other links ==
* [http://analytics.google.com/ analytics.google.com]
* [https://cloud.digitalocean.com/ cloud.digitalocean.com]

Tech Info

2020-02-21T23:22:36Z

Kieran: added tools

Information on this page is intended for the Tech Team.

== Email Accounts ==
* STAR's emails are managed via [https://admin.google.com/standrewsradio.com admin.google.com/standrewsradio.com]
* STAR has a G Suite legacy account (i.e. created before December 2012), allowing the creation of unlimited free accounts, each with 15GB of storage.
** We started using G Suite around May 2008 (citation needed)
* Email addresses for committee members should follow forename.surname@standrewsradio.com.
* There are also multiple groups, e.g. news@, music@, programming@, and hello@. Committee members can be added to groups to receive emails sent to the group. Emails cannot be sent from a group address.
* Both users and groups may have aliases, e.g. bo@ redirects to manager@.
* The invalid user account, *@, will catch any emails sent to non-existent addresses within our domain. This is useful for unlocking old STAR pages connected to long-departed committee members.

== Stream URLs ==
* MP3: [https://garfield.standrewsradio.com:8081/stream/1.mp3 garfield.standrewsradio.com:8081/stream/1.mp3]
* Ogg: [https://garfield.standrewsradio.com:8081/stream/1.ogg garfield.standrewsradio.com:8081/stream/1.ogg]

== Domains ==
* STAR also owns [http://standrewsradio.co.uk standrewsradio.co.uk]; it should simply redirect to the main site.
* Domains are managed by Rachel Hughes, Union Design & Marketing Manager ([mailto:sadesign@st-andrews.ac.uk sadesign@st-andrews.ac.uk])
* The rapid.standrewsradio.com subdomain was associated with RapidSwitch; STAR moved from RapidSwitch to DigitalOcean in 2019, so no rapid. URLs should now be in use.

== Subdomains ==
* [https://studio.standrewsradio.com studio.standrewsradio.com]: the version of the Buzzbox displayed in the studio, showing listener counter and help section.
* [https://listen.standrewsradio.com listen.standrewsradio.com]: a separate version of the Buzzbox.
* [https://buzzbox.standrewsradio.com/ buzzbox.standrewsradio.com]: the listen. subdomain without the STAR logo at the top.
* [https://help.standrewsradio.com/ help.standrewsradio.com]: contains the help section, which is also shown within the studio. subdomain.
* [http://archive.standrewsradio.com/ archive.standrewsradio.com]: you are here.
* [https://status.standrewsradio.com/ status.standrewsradio.com]: website status (subdomain created 5th Feb 2020).
* [https://manage.standrewsradio.com/ manage.standrewsradio.com]: .svg version of 2012 Gorilla Joe logo.
** [https://manage.standrewsradio.com/grafana manage.standrewsradio.com/grafana]: graph of listener stats (Grafana removed 5th Feb 2020 due to unreliability and a planned move to Google Analytics).
** [http://manage.standrewsradio.com/icecast manage.standrewsradio.com/icecast]: global server stats, and list of mount points.
** [https://manage.standrewsradio.com/netdata manage.standrewsradio.com/netdata]: extensive server stats.

== Tools ==
* [Podcast Recorder]: shell script that records, stores and cleans up archived podcasts.
* [https://github.com/Kezz101/ic2ga ic2ga]: Java programme that forwards Icecast statistics to Google Analytics.
* [Stream Status]: PHP page that checks if the stream is currently silent.

== Other links ==
* [http://analytics.google.com/ analytics.google.com]
* [https://cloud.digitalocean.com/ cloud.digitalocean.com]

How to edit the Timeline

2019-09-26T17:28:11Z

Kieran: Created page

Sadly, this page doesn't contain any information on how to manipulate time itself. Instead, you'll have to make do with a simple guide on how to edit the timeline featured on the Starchive. This timeline is powered by [https://timeline.knightlab.com/ Knightlab's Timeline] software. Although it might look scary, if you know how to edit a spreadsheet then editing the timeline won't be hard at all.

== Accessing the timeline ==
The content of the timeline exists in a Google Sheets document that is available at [https://docs.google.com/spreadsheets/d/1gMg_qNhxIp42OQ-u31wVqJl_89Io0rIPBPb0dKfF9cs/edit#gid=0 this link]. Anyone can edit this spreadsheet and changes made will automatically appear on the Starchive website, so please be careful about what you enter!

If you are making big changes to the timeline, you may find it helpful to duplicate the spreadsheet by clicking '''File → Make a Copy'''. This will create a copy of the current timeline in a spreadsheet that you can safely edit. Once you are done editing, simply copy the contents of your spreadsheet back into the master spreadsheet. This will help ensure that no unfinished changes make their way onto the Starchive website.

== Editing the timeline ==
For a brief overview of how to edit the timeline, you can watch [https://vimeo.com/knightlab/timelinejs#t=36s this video] from the Knightlab team. This link starts the video from 36 seconds, skipping the parts that you don't need to worry about. This video also ends up talking about how to publish the timeline - you don't need to worry about that either. All you need to do is edit the spreadsheet and everything else will be done for you.

== Frequently asked questions ==
Below is a section of questions that might crop up whilst you are editing the timeline. This guide was written before the Starchive was launched, so don't get too upset if your question isn't mentioned below. If you do have any queries or problems, simply [mailto:tech@standrews.ac.uk email the Tech Team].

=== Someone deleted my work? ===
Luckily for you the timeline is written in Google Sheets. Alongside the Google Sheets software is an extensive version history that you can access by pressing '''File → Version History'''. This will allow you to revert any unwanted changes and find out who has been messing with your hard work.

=== I can't access the spreadsheet? ===
Make sure that you are logged into your ''standrewsradio.com'' email address. If you aren't, you won't be able to access the spreadsheet. If you don't have such an email address but still want to help out, [mailto:tech@standrewsradio.com contact the Tech Team].

=== My edits aren't showing up on the Starchive? ===
Due to the way spreadsheet publishing works, changes made to the spreadsheet are only transferred to the timeline every five minutes.

[[Category:Starchive Guides|Timeline]]

Main Page

2019-09-26T17:04:03Z

Kieran: Added getting started links

<strong>Welcome to the Starchive Wiki.</strong>

Here lies everything within the Starchive that doesn't belong to the gallery, timeline, websites or podcasts sections. Additionally, this wiki also contains handy guides on how to upload new memories into the Starchive. As editing the Starchive is restricted to pre-approved users, these guides probably won't be too handy for most people, however, feel free to have a look if you're interested in how the Starchive works.

This wiki will be updated periodically with a whole host of new information as and when it becomes available. For more information, or if you've got memories of your own to submit, please contact the Tech Team using the contact button below.

----

=== Getting Started ===
* [[:Category:Starchive Guides|Guides to contributing to the Starchive]]
* [mailto:tech@standrewsradio.com Contact the Tech Team]

Category:Starchive Guides

2019-09-26T16:40:41Z

Kieran: Created category

This category contains a collection of guides available that should help in updating the Starchive. These guides may be updated at any time and new guides might appear too.

Guide to Starchive Gallery

2019-09-26T16:33:23Z

Kieran: Created page

The Starchive Gallery is the home for pictures, photos, art and more to be stored for all to remember forever. The gallery is run using [https://piwigo.org/ Piwigo], an open-source, web-based gallery software. In order to upload or update the contents of the gallery, you will need to login by pressing the login button on the bottom right of the gallery. If you don't have an account with the gallery, please contact the [mailto:tech@standrewsradio.com tech team].

== Uploading images ==
There are multiple different ways to upload to the gallery. If you're just uploading a few photos, and are happy to put them into albums manually, the web uploader is the easiest way. Otherwise, if you're looking to upload to the gallery in bulk, you can also connect via FTP or by one of the many external applications that provide upload capabilities.

=== Uploading via web ===
Uploading images via the web is the quickest and easiest way to upload. Once you have logged in, press '''Add''' underneath the '''Photos''' menu. Once you have selected or created a new album, you can select the photos you would like to upload using the '''Start upload''' button.

=== Uploading via FTP ===
If you have an incredibly large number of images that need to be uploaded, the best way to do this is to see if there are any other applications that provide Piwigo upload capabilities. However, if none of the applications help you, you can upload your images using FTP. Please contact a member of the [mailto:tech@standrewsradio.com tech team] for more information and assistance.

=== Other ways to upload ===
Piwigo provides a list of many other methods that can be used to upload images to the gallery. There are a range of different software available, including apps for your Android/iOS device, programmes for Windows/Mac and plugins for photo editing software like Shotwell and Lightroom. Once you're on the '''Add''' page, click the '''Applications''' and browse through the list of available programmes that might be able to assist you.

== Further administration ==
On the admin dashboard, there are plenty of other tools you can use to edit the gallery. The best way to figure stuff out is to have a poke about and see what can be done. There is also plenty of support and guides available online. However, the documentation available on the Piwigo website is pretty lacking, so if you're looking for guides and tours of the many useful features, press the '''Help me''' button on the top right of the admin dashboard.

[[Category:Starchive Guides|Gallery]]

MediaWiki:Sidebar

2019-09-26T15:30:25Z

Kieran: Removing help

* navigation
** mainpage|mainpage-description
** recentchanges-url|recentchanges
** randompage-url|randompage
* SEARCH
* TOOLBOX
* LANGUAGES

Main Page

2019-09-26T13:36:41Z

Kieran: Initial edit

Main Page

2019-09-26T13:31:58Z

Kieran: Protected "Main Page": High traffic page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]