Browse Source

Initial commit

initial demo
Cian Butler 5 years ago
committed by butlerx
100 changed files with 5331 additions and 0 deletions
  1. +33
  2. +79
  3. +1
  4. +9
  5. +22
  6. +4
  7. +4
  8. +4
  9. +5
  10. BIN
  11. +63
  12. +71
  13. BIN
  14. +62
  15. +133
  16. +38
  17. +24
  18. +6
  19. +50
  20. +5
  21. +5
  22. +5
  23. BIN
  24. BIN
  25. BIN
  26. BIN
  27. BIN
  28. BIN
  29. +19
  30. +23
  31. +42
  32. +14
  33. BIN
  34. BIN
  35. +3
  36. +4
  37. +14
  38. +40
  39. +18
  40. +14
  41. +4
  42. +53
  43. +674
  44. +107
  45. +161
  46. +21
  47. +676
  48. +732
  49. +61
  50. +32
  51. +41
  52. +5
  53. +11
  54. +12
  55. +5
  56. +12
  57. +152
  58. +34
  59. +121
  60. +25
  61. +53
  62. +65
  63. +6
  64. +3
  65. +3
  66. +42
  67. +22
  68. +14
  69. +13
  70. +20
  71. +8
  72. +47
  73. +41
  74. +44
  75. +120
  76. +40
  77. +1
  78. +1
  79. +1
  80. +39
  81. +1
  82. +1
  83. +1
  84. +57
  85. BIN
  86. +8
  87. +36
  88. +21
  89. +8
  90. +27
  91. +233
  92. +25
  93. +36
  94. +41
  95. +139
  96. +119
  97. +48
  98. BIN
  99. BIN
  100. +194

+ 33
- 0
.gitignore View File

@@ -0,0 +1,33 @@
# Logs

# Runtime data

# Directory for instrumented libs generated by jscoverage/JSCover

# Coverage directory used by tools like istanbul

# Grunt intermediate storage (

# node-waf configuration

# Compiled binary addons (

# Dependency directory

# Optional npm cache directory

# Optional REPL history

+ 79
- 0
_config.yml View File

@@ -0,0 +1,79 @@
# Site
title: Redbrick
subtitle: DCU's Networking Society
description: Redbrick is DCU’s Computer Networking society. We host events for everything computing related this ranges from; how to setup your own website and storing your photos online to System Administration and Computer Programming Tutorials. We also host a number of services for our membership.
author: Redbrick
language: en-GB
timezone: Europe/Dublin

root: /~butlerx/demo/
permalink: :year/:month/:day/:title/

# Directory
source_dir: source
public_dir: public
tag_dir: tags
archive_dir: archives
category_dir: categories
code_dir: downloads/code
i18n_dir: :lang

# Writing
new_post_name: # File name of new posts
default_layout: post
titlecase: false # Transform title into titlecase
external_link: true # Open external links in new tab
filename_case: 0
render_drafts: false
post_asset_folder: true
relative_link: false
future: true
enable: true
line_number: true
auto_detect: false

# Category & Tag
default_category: uncategorized

# Date / Time format
## Hexo uses Moment.js to parse and display date
## You can customize the date format as defined in
date_format: DD/MM/YYYY
time_format: HH:mm:ss

# Pagination
## Set per_page to 0 to disable pagination
per_page: 10
pagination_dir: page

# RSS Feed
type: atom
path: atom.xml
limit: 20

# Extensions
## Plugins:
## Themes:
theme: tranquilpeak

# Deployment
## Docs:
- type: git
- type: rsync
user: butlerx
root: ~/public_html/demo/
delete: true

+ 1
- 0
File diff suppressed because it is too large
View File

+ 9
- 0 View File

@@ -0,0 +1,9 @@
title: Redbrick
subtitle: DCU's Networking society
date: 2016-04-10
template: index.html
keywords: redbrick, dcu, school of computing, networking
changefreq: daily
priority: 0.9

+ 22
- 0
package.json View File

@@ -0,0 +1,22 @@
"name": "Redbrick-site",
"version": "0.0.1",
"private": false,
"hexo": {
"version": "3.2.0"
"dependencies": {
"hexo": "^3.2.0",
"hexo-deployer-git": "^0.1.0",
"hexo-deployer-rsync": "^0.1.1",
"hexo-generator-archive": "^0.1.4",
"hexo-generator-category": "^0.1.3",
"hexo-generator-feed": "^1.1.0",
"hexo-generator-index": "^0.2.0",
"hexo-generator-tag": "^0.2.0",
"hexo-renderer-ejs": "^0.2.0",
"hexo-renderer-marked": "^0.2.10",
"hexo-renderer-stylus": "^0.3.1",
"hexo-server": "^0.2.0"

+ 4
- 0
scaffolds/ View File

@@ -0,0 +1,4 @@
title: {{ title }}

+ 4
- 0
scaffolds/ View File

@@ -0,0 +1,4 @@
title: {{ title }}
date: {{ date }}

+ 4
- 0
scaffolds/ View File

@@ -0,0 +1,4 @@
title: {{ title }}
date: {{ date }}

+ 5
- 0
scaffolds/ View File

@@ -0,0 +1,5 @@
title: {{ title }}
date: {{ date }}

source/.DS_Store View File

+ 63
- 0
source/_posts/ View File

@@ -0,0 +1,63 @@
title: Week 22 - New Committee | Birthday
author: butlerx
date: 2016-04-04
- announce
- birthday

Hi all:

We’ve had a busy week with a talk, quiz and the AGM. Last week was the AGM or
the shuffling of Committee, when we say good bye to some old faces and hello to
some new ones. As those of you who attended the AGM know, I was appointed as
Redbrick’s new and shiny secretary, I look forward to a year writing badly
worded but informing announces for my adoring public.
Now down to business…

<!-- more -->
- Redbrick 20th Birthday - Saturday 09/04 - Opium Cafe - 19:00

AGM Results

The results of the AGM election on Thursday are as follows:

- Noah Donnelly (cac) - Chair
- Cian Butler (butlerx) - Secretary
- Ross O'sullivan (sully) - Treasurer
- Cliodhna Harrison (thegirl) - Events
- Liam Rooney (ginger) - PRO
- Cormac Smartt (pints) - Helpdesk
- Lorcan Boyle (zergless) - Admin
- Richie Walsh (koffee) - Admin

Redbrick 20 th Birthday
- Date: Saturday 09/04
- Time: 19:00
- Location: Opium Cafe, Wexford Street, Dublin
- More info:

The cake has been ordered, showers have been had, cat sitters have been arranged
and the hoodies have been ironed…. Yes that’s right, Redbrick’s 20th birthday is
just around the corner! The event is taking place this very Saturday at Opium
Cafe in town so head on over to the birthday website to reserve your ticket if
you haven’t already done so. We look forward to seeing both students and
associates for a few drinks and a bit of gossip. Any questions? Just give us a

We are all looking forward to seeing you.

As always, keep your eyes peeled on the lovely calendar and social media pages:
- Twitter: @RedbrickDCU
- Facebook:
- Snapchat: RedbrickDCU
- Calendar:

Hoping you have a good week from all of the Redbrick Committee.
Bye for now.

+ 71
- 0
source/_posts/ View File

@@ -0,0 +1,71 @@
title: Week-4
date: 2014-10-13
author: kylar
- announce
- intercom
- screen
- associate
thumbnailImage: intercom.png
thumbnailImagePosition: right
autoThumbnailImage: yes

= Screen@Redbrick =
We've had to postpone this as we have admin exams at 6pm.
So we're going to reschedule for next week and change up the movie to the cheesy
1995 classic "Hackers" Sorry for the inconvenience, we'll make sure you guys get
all of next week's details sooner. We're still ironing out a few bugs on this
<!-- more -->
= Associate Talks: elephant =
Topic: "Spammers Hate Him! One weird trick for staying secure online"
When: Tuesday 14th October at 18:00
Where: C115

Social media accounts are valuable to scammers and spammers, who want to make a
quick buck off your reputation. Here's a few tips to help make your accounts
harder to abuse so hold on to your tinfoil hats kids Diarmaid MacManus will be
talking to us about how to stay secure online, some of the tips and tricks he's
learned from his time in application security with various multinationals. If
you don't leave this talk paranoid we'll be surprised!

= Helpdesk Talks =
Topic: How to get up and running with Redbrick.
Where: LG25
When: Wednesday 15th October 15:00
Cian Butler will be guiding you through your first steps using Redbrick
services. He'll be walking through how to use your webspace, logging into IRC
and how to run programmes on our development servers. With the rest of the
committee on hand to help out we should have you up and running in no time.

= Intercom@Redbrick =
{% image nocaption right intercom.png intercom%}
This week we see another company come to pay us a visit; this week it's
Intercom has only recently had its 3rd birthday, yet it's making huge a serious
impact on how companies deal with their customers. Intercom have had developers,
engineers and business join them from companies as big as Amazon and
Google. Come along on Thursday and see how Intercom do what they do, and
what it's like to work for them.

We've got:
Brian White and Brian Long (make sure to call him Robin) coming to talk
about running Intercom.
Matthew Barrington will be fanboying to the extreme about his time with

This should be a great evening, for anyone that may have been at the
inside intercom meetings throughout the year you know how interesting and
enthusiastic the Intercomrades are; for those who haven't you should
definitely come along and witness it first hand.

Don't forget to keep an eye on our various social media soapboxes:
- Twitter @RedbrickDCU
- Facebook:

source/_posts/week-4/intercom.png View File

Before After
Width: 370  |  Height: 111  |  Size: 12 KiB

+ 62
- 0
source/about/committee/ View File

@@ -0,0 +1,62 @@
title: Committee
date: 2016-04-17 16:22:40

<sub> - [About](../) - [Committee](../committee) - [Constitution](../constitution) - [Regulations](../regulations) - [Contact](../contact) - [Past Committees](../past-committees) -</sub>

The Committee is a 12 person team which is elected yearly to run all aspects of
the society

Chairperson: Noah O' Donnaile (cac)
Secretary: Cian Butler (butlerx)
Treasurer: Ross O' Sullivan(sully)
Events Officer: Cliodhna Harrison (thegirl)
Public Relations Officer: Liam Rooney (ginger)
System Administrators: Richard Walsh (koffee) & Lorcan Boyle (zergless) & TBD
Webmaster: TBD
Helpdesk: Cormac Smartt(pints) & TBD
First Year Rep: TBD

## Helpdesk
The Helpdesk is made up of the friendly team of two Cormac Smartt(pints) & our
second Education officer (Helpdesk) will be elected at an EGM to come.

The Helpdesk is what it sounds like, a desk for help. No seriously, we're here
to help out and answer any questions at all to help you make the most of
Redbrick. Don't be shy now, feel free to mail or hey us any time and check out
the help section we maintain.

We also run regular tutorial in the CA labs in DCU, any member can attend and we
will guide you through the basics and answer any queries, watch out for notices
and posters around campus or on RedBrick.

The Helpdesk tutorials start [here](

## Admins
An elite team of individuals dedicated to keeping the society's hardware and
services running. The Admin team is made up of three elected Admins and the
Webmaster who are current members of the Committee, as well as previous elected
root holders who have volunteered to keep doing stuff.

Elected System Administrators:
- Richard Walsh (koffee)
- Lorcan Boyle (zergless)
- To Be Elected - Click here if you're <a href="[sent from website]"target="_top">interested</a>.

Esteemed Holders Of Root:
- tbolt
- voy
- Lorcan Boyle (zergless)
- Emmanuel Caillé (Twister)
- Richard Walsh (koffee)
- vadimck
- isaac702
- gw
- fun
- haus
- receive
- werdz
- johan
- sonic
- lil_cain

+ 133
- 0
source/about/constitution/ View File

@@ -0,0 +1,133 @@
title: Constitution
date: 2016-04-17 16:22:40

<sub> - [About](../) - [Committee](../committee) - [Constitution](../constitution) - [Regulations](../regulations) - [Contact](../contact) - [Past Committees](../past-committees) -</sub>

## DUBLIN CITY UNIVERSITY: Dublin City University Networking Society CONSTITUTION
## 1. Name of Society:
1. The official name of the society will be Dublin City University Networking Society. this shall appear on correspondence with official bodies.
1. The society operates under the name Redbrick.

## 2. Aims & Objectives:

The aims and objectives of the Society are as follows:
1. To facilitate computer networking in all its forms.
2. The promotion of electronic communication and related computer systems in all its forms.
3. To foster the development of members.
4. To provide a forum for members to interact and socialise through activities and discuss and gain experience in computer networking.
5. To assist Society members to represent the Society at a higher level.
6. To increase and promote awareness of electronic communication and related computer systems.
7. To help educate people in the usage of Internet utilities and resources.

## 3. Members:
1. Membership of the Society shall be open to all students, staff and former
students of the University,
2. Membership shall be obtained by paying the appropriate fee and registering with the OSL Database for the current academic year.
3. The Society recognizes the important role that former students and staff can play in Societies . Therefore there shall be a class of “Associate Member” of the Society for former students of the University and staff.
4. Associate Members shall pay an annual membership fee to the Society. The amount of this fee shall not be less than the ordinary membership fee and no more than 10 (ten) times the ordinary membership fee.Application for a higher Associate Member fee made be made to the OSL by the Society involved.
1. In consultation with OSL as outlined (see section 3.4) associate members shall pay an annual membership fee that will be twice that of the ordinary membership fee.This will be re-evaluated in the event of a change to the ordinary membership fee.
5. Associate Members are not eligible for election to the Society’s Governing Executive committee
6. Associate Members shall be entitled to attend all general meetings of the Society but have no voting rights. The rights of an Associate Member shall not exceed those of an ordinary member of the Society
7. All members shall be bound by this constitution
8. Honorary lifetime membership is awarded to the founding committee members.
9. Nothing in this section shall prevent the society bestowing honorary membership upon a graduate or former student of Dublin City University.

## 4. Governing Executive Committee:
1. The Society shall have a Governing Executive Committee all of whom must be fully registered students of DCU (The Committee).
2. The Committee shall run the Society of behalf of its members and in accordance with the aims and objectives.
3. Although decisions should be arrived at by the consensus of the committee (where possible), committee decisions shall be decided by majority voting.
4. A quorum shall be ⅔ of committee members.
5. The following Officer positions are obligatory on the Committee :
- Chairperson
- Secretary
- Treasurer
- Public Relations Officer
_Other suggested positions include:_
- 3x Systems Administrators
- 2x Helpdesk
- 1st Year Liaison Officer
- Events Officer
- Webmaster
6. The Term of Office of these elected officers shall be one academic year.
7. No student may hold an obligatory Officer (as above) position for more than two consecutive years.

## 5. Election of the Governing Executive Committee:
1. The Committee Members shall be democratically elected at the Annual General Meeting (AGM) or at an Extra-ordinary General Meeting (EGM).
2. To seek election to the Committee, each candidate must have two nominations by current members of the Society.
3. To be deemed fit for election to the position of Systems Administrator or Webmaster, the candidate must either:
1. Pass an Aptitude test, as devised by the outgoing webmaster for webmaster candidates, or system administrators for system administrator candidates. If it is deemed preferable to do so, the test may be set by a third party nominated by the webmaster (in the case of the webmaster examination), or by a majority of the system administrators (in the case of the system administrator exams). The current committee will nominate this third party. Be an outgoing Webmaster or Systems Administrator
4. All Helpdesk candidates must sit and pass a test as devised by the outgoing education officer(s)

## 6. Duties of the Governing Executive Committee:
1. The Chairperson shall be the Chief Officer of the Society whose functions include chairing all meetings of the committee and officiating at meetings of the Society.
2. The Chair of any meeting shall have an ordinary vote at committee meetings and meetings of the Society. In the event of a tied vote on any matter she/he shall have the casting vote.
3. The Secretary’s function shall be to deal with all correspondence and records of the Society.
4. The Secretary keeps minutes of all committee meetings, of all general meetings, of the Annual General Meeting or any other meetings related to the business of the Society when requested by the committee.
5. The Secretary may keep a record of authorization of expenditure.
6. The Secretary shall give notice to all members of the Society's’ meetings, events, and functions.
7. The Secretary shall assist the Public Relations Officer (PRO) or other officers to organize fundraising events and sponsorship where necessary.
8. The Treasurer’s function shall be to administer the funds of the Society and to maintain accounts and budgets.
9. The Treasurer shall be responsible for the maintenance of accounts subject to the decision of the committee in compliance with the relegations set down by the Society Life Committee.
10. The Treasurer shall keep full records of income and expenditure of the Society. The Treasurer shall also keep a record of who authorized various expenditures and shall issue receipts.
11. The Treasurer must countersign all cheques and withdrawal forms for the Society’s bank account.
12. Where the Treasurer is decreed as unavailable, another designated person may countersign cheques and withdrawal forms for the Society in consultation with the Society Life Committee.
13. The Public Relations Officer (along with the Secretary) shall be responsible for the advertising of all functions of the Society through all means possible.
14. The System Administrators shall be held ultimately responsible for the administration, security, and maintenance of the society's computer systems. They shall be responsible for the notification of the committee in regard to any breaches of the rules and regulations of the system. They are hereby authorised to take any administrative action necessary to discharge their duties, so long as such actions are constitutional. Such actions are open to review by the committee.
15. The Webmaster shall be responsible for the design, implementation, and maintenance of the web site. They shall work in conjunction with other members of the committee in order to publicise society details via the web.
16. The Helpdesk's role is to answer the system-related questions of the society's membership, and to detail, organise, and implement beneficial tutorials for the members.
17. The Events Officer shall have the responsibility of organising all receptions held by the society.
18. 1st Year Liaison Officer shall work with the committee to make the society more accessible for first years. As part of this they shall work with the Events, Public Relations & Helpdesk where applicable. The 1st Year Liaison Officer shall be elected at an EGM in semester one, and must be in their first year as an undergraduate student at DCU
19. The committee shall endeavour to meet fortnightly during term time, at which a majority of the committee must attend.
20. Any committee member that misses more than 3 committee meetings without the permission of the chair will be deemed to have reasonable grounds for dismissal

## 7. Dismissal and Resignation of Committee Members:
1. No member of the committee shall be dismissed from office unless:
1. Written notice of a resolution to seek such a dismissal, signed by 10% of the members of the Society is received five working days prior to a general meeting at which such a resolution shall be debated.
2. ⅔ of the Governing Executive Committee may also call a meeting to debate the dismissal of another committee member.
2. A resolution to dismiss a committee member shall be passed by a simple majority voting at the relevant and quorate meeting.
3. A committee member wishing to resigned must submit a letter in writing declaring that intention to resign to the Secretary, who will immediately inform the committee as a whole. The responsibilities of that person shall be delegated to other committee member(s) until a by- election can be held to re-elect a new person to the position.

## 8. Meetings:
1. There shall be an Annual General Meeting (AGM) held each year where the committee member shall be elected
2. The AGM shall be held no later than in the final month of the Academic year.
3. A quorum of a meeting shall be a majority of the committee members and the square-root of the number of ordinary members, rounded-up.
4. The business of the AGM shall include elections of relevant Executive Governing Committee as well as annual reports from the outgoing Governing Executive Committee (which should include a Treasurer’s report on the finances of the Society).
5. An Extra-ordinary General Meeting (EGM) shall be convened if:
1. 10% of the ordinary membership of the Society requests such a meeting in writing.
2. A quorum of the Governing Executive Committee requests such a meeting in writing.
3. A vacancy on the current committee occurs and there is a need to elect a replacement.
6. Notice of all meetings shall be given to the membership at least five working days prior to the date of the meeting.
7. At a meeting, a member may propose a resolution relating to the business of the Society. The resolution shall be voted on by a show of hands and a declaration of the Chairperson that the resolution is carried (unless a secret ballot is demanded by any 5 members) shall be conclusive evidence that the resolution has passed or failed.
8. In the event that the Chairperson’s resolution (8.7) is challenged a recount of the votes will be administered in which a number of appropriate people will be appointed by the committee as “tellers” to count the votes. The result will be announced by the Chairperson or the Vice-Chairperson (where requested by the general meeting).
9. No resolution may contravene DCU, DCU OSL or CLC policy.

## 9. General:
1. There shall be a President of the Society who shall be a staff member in compliance with the regulations set down by the Society Life Committee
2. The membership fee for the Society shall be in compliance with the conditions set down by the OSL
3. Each member of the Society shall be entitled to receive a copy of this Constitution, on demand, free of charge.
4. In the event of a clash with the Society Life Committee Constitution, the Society Life Committee Constitution shall take precedence above this constitution and is subject to the Society Life Committee at all times.
5. There is no provision for a Society to amend this Constitution.
6. In joining the Society, members agree to be bound by the rules and regulations of the Society as laid down in this constitution and by the Governing Executive Committee. Members violating these rules and regulations
shall be answerable to the committee and may have
1. Computer system account suspended for a period of time decided by the System Administrators.
2. Their membership revoked and no monies refunded, for persistent breaches or extremely serious breaches, as deemed by a majority of the committee. In the event that the committee cannot resolve a dispute with a member(s), The Society Life Committee shall rule on the matter and its decision is final.

## 10. Equipment.
1. Any equipment loaned to the society by individuals may only be withdrawn if:
1. Notice is given by the individual at least two weeks prior to the date of withdrawal.
2. Or by the express approval of a committee majority.
2. The society shall seek to return any loaned equipment.
1. Any equipment donated to the society shall therein be the property of the society.
2. Any equipment which is damaged or destroyed whilst on loan to the society will have its replacement cost paid to it's loaner.
3. Administration of loaned or donated equipment shall be the exclusive responsibility of the committee.

+ 38
- 0
source/about/contact/ View File

@@ -0,0 +1,38 @@
title: Contact & Services
date: 2016-04-17 16:22:40

<sub> - [About](../) - [Committee](../committee) - [Constitution](../constitution) - [Regulations](../regulations) - [Contact](../contact) - [Past Committees](../past-committees) -</sub>

### Redbrick Admin Team
- This address can be used to contact the Admin team if you have any requests regarding your account or any special service requests.
- Please provide your Redbrick username (if applicable or you are not using your Redbrick email address) and in the case of getting unsubscribed to a mailing list the mailing list's name and the email subscribed is very important.
- Email the Redbrick <a href="[sent from website]"target="_top">Admin Team</a>

### Helpdesk Team
If you have any queries about the functionality of your Redbrick account, or if you have any issues you want explained, you can contact the <a href="[sent from website]"target="_top">Helpdesk Team</a>.

### Accounts And Finance
Enquiries regarding membership and financing should be directed to our
<a href="[sent from website]"target="_top">Treasurer</a>.

### Webgroup/Webmaster
If you would like to get involved with the Webgroup (more information [here][4]) or
have web-related Redbrick queries, please email the <a href="[sent from website]"target="_top">Webmaster</a>.

### Committee
If there is a general matter you wish to raise with the Committee please Email
use <a href="[sent from website]"target="_top">here</a>.

### Abuse
If there is a matter you would like to raise with committee concerning the abuse
of redbrick services you can contact committee <a href="[sent from website]"target="_top">here</a>.

## Discussion Lists
Redbrick hosts many discussion and announce lists which can be viewed [here][1]. Two lists members may find interesting are the [admin discussion][2] list and the [trainee admin][3] list.


+ 24
- 0
source/about/ View File

@@ -0,0 +1,24 @@
title: About Redbrick
date: 2016-04-17 16:22:40

<sub> - [About](../about) - [Committee](./committee) - [Constitution](./constitution) - [Regulations](./regulations) - [Contact](./contact) - [Past Committees](./past-committees) -</sub>

Redbrick is DCU's Computer Networking society. We host events for everything computing related this ranges from; how to setup your own website and storing your photos online to System Administration and Computer Programming Tutorials. We also host a number of services for our membership.

## A Brief Redbrick History
In October of 1995 a group of friends started the ball rolling on the idea of a computer network in [DCU][1], run by students for the students. Starting out with a battered 386 PC (dubbed Nurse), bits of borrowed memory, their own cash, and a lot of luck, they went about organising the DCU Networking Society. Once recognised as a society, they were allowed to setup a temporary home for our server in the [Computer Applications][2] faculty. With the approval of John Boland, the then head of [Computer Services][3] in DCU, the society received its own subnet, dubbed RedBrick, along with a physical area in which to store Nurse, our one and only machine. Since April 9th 1996, when the machine went officially online, the society itself has grown rapidly. So rapidly in fact, that we are one of the largest societies on/off campus!

RedBrick's social side has grown a lot also, with the society celebrating its [20th Anniversary][4] back in April 2016. The society continues to run their annual Freshers Ball, Halloween Party, Christmas Party and Tech Week throughout the year.

As one of the biggest societies in DCU, we're always looking for new membership. The membership fee itself is a paltry &euro;4.00 until Clubs & Socs Day 2 (generally mid Feburary) when the membership cost drops to &euro;2.00! However outside of Clubs & Socs days it becomes a little awkward to sign up, but it is more than doable - check [here][5] for details on how to pay.
Our current main server is [Azazel][6], with Pygmalion also providing login services to users. See the [RedBrick Hardware Inventory][7] for descriptions of our servers and other equipment.

[5]: ../help/joining

+ 6
- 0
source/about/past-committees/ View File

@@ -0,0 +1,6 @@
title: Past Committee
date: 2016-04-17 16:22:40

<sub> - [About](../) - [Committee](../committee) - [Constitution](../constitution) - [Regulations](../regulations) - [Contact](../contact) - [Past Committees](../past-committees) -</sub>

+ 50
- 0
source/about/regulations/ View File

@@ -0,0 +1,50 @@
title: Regulations
date: 2016-04-17 16:22:40

<sub> - [About](../) - [Committee](../committee) - [Constitution](../constitution) - [Regulations](../regulations) - [Contact](../contact) - [Past Committees](../past-committees) -</sub>

1. Members wishing to run networked programs must first obtain the permission of the committee. The committee reserves the right to shut down such programs without notice.
2. Members wishing to make an announcement to the membership are encouraged to use the Newsgroup system, but in cases where mailing the membership is considered vital, the permission of the committee must be obtained first.
3. Spamming other users is an offense (e.g. mass mailing, system-wide write messages, or flooding chat rooms) unless a practical need to do so has been presented to the committee, and their permission obtained for such a mass communication.
4. Users are requested to take all reasonable precautions to ensure the security of their account, and to comply with the instructions of Redbrick's System Administrators and with their guidelines on security.
5. The reprovision of Dublin City University Networking Society Services or Equipment requires the approval of the committee.
6. Certain file types are banned by our web server and users should not try to circumvent this rule. For more information on the restricted file types and ggetting access, contact<a href="[sent from website]"target="_top"> helpdesk</a>.

The following regulations are additional to the Society's own rules...
- [Code of Conduct for the use of Computing Resources in Dublin City University[1]
- [HEAnet Acceptable Usage Policy][2]

## Reasoning
- These regulations are for the protection of the system and the society. We have a small but dedicated Admin team.
- Regulation 1, about networked programs, is primarily for security reasons. Networked programs are programs which allow non-system users to interact with them, say via TCP/IP. There is an inherent security risk here.
- Regulations 2 and 3 are self-explanatory, spam is not on!!
- Regulation 4 should be an obvious assumption for any accounts you hold.
- Regulation 5 is simply to safeguard that we can control what services are provided to others (similar to regulation 1), only the Admin team can really judge what we can support. Also, private members should not be giving "accounts" to others, their account is for their own use only.

## Rules For #lobby.
Users must obtain the permission of the committee before using bots/scripts in #lobby.
- Users are not to spam the channel.
- Users should not encourage others to enter IRC commands that might be harmful or that produce undesirable effects.
- Users are not to direct people to unsafe or inappropriate links without prior warning of their content.
- Ops are, as a general rule, a committee privilege. While they may be used by others on occasion, they are only for administrative/emergency use. Abuse of ops will lead to their removal.
- Offences shall be dealt with by the committee and may lead to banning, repeated offences may lead to disuserment.
- Ops should endeavour to use common sense when enforcing the rules.

## Authorized Bots in #lobby
- mincebot
- teh
- creadak

## User Agreement
By logging into Redbrick you agree to these terms and conditions.

1. Redbrick is governed by various regulations, as detailed above
2. Redbrick take no responsibility for the integrity of user data stored or developed using Redbrick. While Redbrick will endeavour to provide a backup service to all users, Redbrick cannot ultimately guarantee protection from system failures, user accidents or malicious activities by other users. So please don't leave the only copy of your 4th year final project on Redbrick! :o) Redbrick offers no guarantee of user privacy. Redbrick administrators have the power to search accounts and all user data therein for any material that is considered to be illegal (by the regulations we mentioned above) or that pose a security threat to other user accounts or even the system as a whole. Redbrick will endeavour to make all user accounts secure by default but it is impossible to `police' all user activities, which may include attempts to `trojan' or subvert other user accounts.
3. Any attempts to undermine or breach the security of Redbrick or any user's account will be taken as a serious matter, and will be subject to appropriate punishment as determined by the committee. Such punishments will typically amount to a disabling of the user's account for a certain period. All other services (events, talks, tutorials) that Redbrick provide to members will of course still be available to the user.
4. Redbrick reserve the right to update this agreement at any time in the future. Should this be necessary, you will be asked to agree to these terms and conditions again with the new agreement replacing previous versions.


+ 5
- 0
source/all-archives/ View File

@@ -0,0 +1,5 @@
title: "all-archives"
layout: "all-archives"
comments: false

+ 5
- 0
source/all-categories/ View File

@@ -0,0 +1,5 @@
title: "all-categories"
layout: "all-categories"
comments: false

+ 5
- 0
source/all-tags/ View File

@@ -0,0 +1,5 @@
title: "all-tags"
layout: "all-tags"
comments: false

source/assets/.DS_Store View File

source/assets/images/intercom.png View File

Before After
Width: 1000  |  Height: 1000  |  Size: 24 KiB

source/assets/images/logo-small.png View File

Before After
Width: 57  |  Height: 46  |  Size: 2.9 KiB

source/assets/images/logo.png View File

Before After
Width: 298  |  Height: 69  |  Size: 11 KiB

source/favicon.ico View File

Before After

source/help/.DS_Store View File

+ 19
- 0
source/help/exams/ View File

@@ -0,0 +1,19 @@
title: Exams
date: 2016-04-17 16:15:35
- help
- exams
- helpdesk
- admin
- webmaster

<sub> - [Helpdesk](../) - [Joining](../joining) - [Tutorials](../tutorials) - [Exams](../exams) -</sub>

If you are thinking of running for the position of Admin, Webmaster or Helpdesk
you must first pass an exam. Here are some exams from previous years.

## Admins Test
## Webmaster Test
## Helpdesk Test

+ 23
- 0
source/help/ View File

@@ -0,0 +1,23 @@
title: Helpdesk
date: 2016-04-17 16:15:35
- help
- helpdesk
- support
<sub> - [Helpdesk](.) - [Joining](./joining) - [Tutorials](./tutorials) - [Exams](./exams) -</sub>

The Redbrick Helpdesk is staffed by our team of highly skilled volunteer
Education Officers.

The Helpdesk write and maintain a series of tutorials on RedBrick's systems.
These are available on our wiki.

The Helpdesk team can also be contacted by Email, and over IRC in the channel #helpdesk. You can access IRC by using one of the methods available here.

The Helpdesk can be emailed at the <a href="[sent from website]" target="_top">Helpdesk Email address.</a>

The Helpdesk Team:
- Cormac Smartt(<a href="[sent from website]" target="_top">pints</a>)
- 1 open position to be filled.

+ 42
- 0
source/help/joining/ View File

@@ -0,0 +1,42 @@
title: Joining
date: 2016-04-17 16:15:35
- join
- help

<sub> - [Helpdesk](../) - [Joining](../joining) - [Tutorials](../tutorials) - [Exams](../exams) - </sub>

Joining Redbrick is easy.

## What is Redbrick?
That's a good question! Redbrick is DCU's Computer Networking Society. Want to know more? Try our [about page!](../../about)

## Who can join Redbrick?
Membership is open to all past and present students and staff of Dublin City University, and St. Pat's, Drumcondra.

## How much does it cost?
Students - €4
Associates - €8
Staff - €8
Guests - €10
## What username can I have?
Almost anything you want - providing the username is available and no more than eight characters in length!

## How can I pay?
Visit our stand on Clubs & Societies day in the first couple of weeks of either semester.
Bank transfer or lodgment - see below for our bank details.
Paypal - see below for our paypal payment form. This is the fastest way to join or renew your membership!
If all else fails, you can arrange to meet a Committee member on-campus.
## Help
If you have any difficulty, please Email <a href="[sent from website]" target="_top">Treasurer</a>.
## Pay By Paypal
In the payment notes, please make sure you provide us with:
- Your __Redbrick username__.
- If you are a new user, we __require__ your DCU student / staff ID number.

<form action="" method="post" target="paypal"><input type="hidden" name="cmd" value="_xclick"><input type="hidden" name="business" value=""><input type="hidden" name="item_name" value="Membership"><input type="hidden" name="item_number" value="Membership Payment"><table id="paypalform"><tbody><tr><td><input type="radio" name="amount" value="4.50"> Student</td><td>€4.00 + 50c Paypal fees</td></tr><tr><td><input type="radio" name="amount" value="8.57"> Associate</td><td>€8.00 + 57c Paypal fees</td></tr><tr><td><input type="radio" name="amount" value="20.00"> Associate(Including Donation)</td><td>€20.00</td></tr><tr><td><input type="radio" name="amount" value="8.66"> Staff</td><td>€8.00 + 64c Paypal fees</td><tr><td colspan="2" align="center"><input type="image" name="submit" src="" alt="Make payments with PayPal - it's fast, free and secure!"></td></tr></tbody></table>
<input type="hidden" name="no_shipping" value="1"> <input type="hidden" name="ah" value="0"> <input type="hidden" name="currency_code" value="EUR"> <input type="hidden" name="bn" value="PayPal_Mike"></form>
## Pay by bank transfer / lodgement
Please contact the <a href="[sent from website]" target="_top">Treasurer</a> to make arrangements to pay via bank transfer.

+ 14
- 0
source/help/tutorials/ View File

@@ -0,0 +1,14 @@
title: Tutorials
date: 2016-04-17 16:15:35
- help
- exams
- helpdesk
- admin
- webmaster

<sub> - [Helpdesk](../) - [Joining](../joining) - [Tutorials](../tutorials) - [Exams](../exams) -</sub>

## How to

themes/.DS_Store View File

themes/tranquilpeak/.DS_Store View File

+ 3
- 0
themes/tranquilpeak/.bowerrc View File

@@ -0,0 +1,3 @@
"directory": "source/_bower_components"

+ 4
- 0
themes/tranquilpeak/.eslintignore View File

@@ -0,0 +1,4 @@

+ 14
- 0
themes/tranquilpeak/.eslintrc.json View File

@@ -0,0 +1,14 @@
"extends": "google",
"rules": {
"comma-dangle": [2,"never"],
"valid-jsdoc": [2, {
"requireReturnDescription": false,
"requireParamDescription": false
"brace-style": [2, "stroustrup"],
"no-trailing-spaces": [2, {"skipBlankLines": true }],
"max-len": [1, 100, 4, {"ignoreUrls": true}]

+ 40
- 0
themes/tranquilpeak/.github/ View File

@@ -0,0 +1,40 @@
# Contributing #

[![Join the chat at](](

All kinds of contributions (enhancements, new features, documentation & code improvements, issues & bugs reporting) are welcome.

## Code style ##

### Javascript

We use [ESLint]( based on Google code style to maintain code style.
Check code status with :
``` bash
npm run eslint
# or
grunt eslint

## Issues ##

When you create an issue to report a bug or ask a question, please include your :

- Operating system with version
- Node version
- Hexo version
- Hexo-cli version
- Tranquilpeak version

and all others related information that are susceptible to help us.

## Pull requests ##

All pull requests must be done on the **dev** branch.

Before a pull request :

- There is no tests yet so verify that your code is running well. Blog generation (`hexo g`) must not outputs errors
- Check code style with eslint.
- Don't forget to update user and/or developer documentation if it's necessary

+ 18
- 0
themes/tranquilpeak/.github/ View File

@@ -0,0 +1,18 @@
<!-- use this template only to report a bug or ask a question -->
<!-- fill this part for bugs reporting or questions -->
### Configuration

- **Operating system with version** :
- **Node version** :
- **Hexo version** :
- **Hexo-cli version** :
- **Tranquilpeak version** :
<!-- fill this part for bugs reporting if needed -->
### Actual behavior

<!-- fill this part for bugs reporting if needed -->
### Expected behavior

<!-- fill this part for bugs reporting if needed -->
### Steps to reproduce the behavior

+ 14
- 0
themes/tranquilpeak/.github/ View File

@@ -0,0 +1,14 @@
<!-- your changes must be compatible with the latest version of Tranquilpeak -->
### Configuration

- **Operating system with version** :
- **Node version** :
- **Hexo version** :
- **Hexo-cli version** :
### Changes proposed


+ 4
- 0
themes/tranquilpeak/.gitignore View File

@@ -0,0 +1,4 @@

+ 53
- 0
themes/tranquilpeak/Gruntfile.js View File

@@ -0,0 +1,53 @@
module.exports = function(grunt) {
// Load the include-all library in order to require all of our grunt
// configurations and task registrations dynamically.
var includeAll;

try {
includeAll = require('include-all');
catch (e0) {
console.error('Could not find `include-all` module.');
console.error('Skipping grunt tasks...');
console.error('To fix this, please run:');
console.error('npm install include-all --save-dev');

* Loads Grunt configuration modules from the specified
* relative path. These modules should export a function
* that, when run, should either load/configure or register
* a Grunt task.
* @param {String} relPath
* @return {function}
function loadTasks(relPath) {
return includeAll({
dirname: require('path').resolve(__dirname, relPath),
filter: /(.+)\.js$/
}) || {};

* Invokes the function from a Grunt configuration module with
* a single argument - the `grunt` object.
* @param {Object} tasks
* @return {void}
function invokeConfigFn(tasks) {
for (var taskName in tasks) {
if (tasks.hasOwnProperty(taskName)) {

// Load task functions
var taskConfigurations = loadTasks('./tasks/config');
var registerDefinitions = loadTasks('./tasks/register');

// Run task functions to configure Grunt.

+ 674
- 0
themes/tranquilpeak/LICENSE View File

@@ -0,0 +1,674 @@
Version 3, 29 June 2007

Copyright (C) 2007 Free Software Foundation, Inc. <>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.


The GNU General Public License is a free, copyleft license for
software and other kinds of works.

The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.

When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.

To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.

For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.

Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.

For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.

Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.

Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.

The precise terms and conditions for copying, distribution and
modification follow.


0. Definitions.

"This License" refers to version 3 of the GNU General Public License.

"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.

"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.

To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.

A "covered work" means either the unmodified Program or a work based
on the Program.

To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.

To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.

An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.

1. Source Code.

The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.

A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.

The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.

The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.

The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding

The Corresponding Source for a work in source code form is that
same work.

2. Basic Permissions.

All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.

You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.

Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.

3. Protecting Users' Legal Rights From Anti-Circumvention Law.

No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such

When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.

4. Conveying Verbatim Copies.

You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.

You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.

5. Conveying Modified Source Versions.

You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:

a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.

b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".

c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.

d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.

A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.

6. Conveying Non-Source Forms.

You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:

a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.

b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.

c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.

d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.

e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.

A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.

A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.

"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.

If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).

The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.

Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.

7. Additional Terms.

"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.

When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.

Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:

a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or

b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or

c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or

d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or

e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or

f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.

All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.

If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.

Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.

8. Termination.

You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).

However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.

Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.

Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.

9. Acceptance Not Required for Having Copies.

You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.

10. Automatic Licensing of Downstream Recipients.

Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.

An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.

You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.

11. Patents.

A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".

A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.

Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.

In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.

If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.

If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.

A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.

Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.

12. No Surrender of Others' Freedom.

If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.

13. Use with the GNU Affero General Public License.

Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.

14. Revised Versions of this License.

The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.

If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.

Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.

15. Disclaimer of Warranty.


16. Limitation of Liability.


17. Interpretation of Sections 15 and 16.

If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.


How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

tranquilpeak-hexo-theme is a gorgeous theme for Hexo static blog
Copyright (C) 2015 Louis Barranqueiro

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program. If not, see <>.

Also add information on how to contact you by electronic and paper mail.

If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:

tranquilpeak-hexo-theme Copyright (C) 2015 Louis Barranqueiro
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".

You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see

The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read

+ 107
- 0
themes/tranquilpeak/ View File

@@ -0,0 +1,107 @@
# Tranquilpeak

[![Join the chat at](](

A gorgeous responsive theme for Hexo blog framework


## Summary ##

- [General](#general)
- [Features](#features)
- [Quick start](#quick-start)
- [Demo](#demo)
- [Documentation](#documentation)
- [Contributing](#contributing)
- [Showcase](#showcase)
- [License](#license)

## General ##

- **Author** : Louis Barranqueiro
- **Version** : 1.7.1
- **Compatibility** : Hexo 3.0.0 or later

## Features ##

**General features :**

- Fully responsive
- Optimized for tablets & mobiles
- Configurable menu of the sidebar
- Pages to filter tags, categories and archives
- Background cover image
- Beautiful about page
- Support Open Graph protocol
- Support internationalization (i18
- Easily customizable (fonts, colors, layout elements, code coloration, etc..
**Posts features :**

- Thumbnail image
- Cover image
- Responsive videos & images
- Sharing options
- Navigation menu
- GitHub theme for code highlighting (customizable)
- Image gallery
- Tags for images (FancyBox), wide images, tabbed code blocks, highlighted text, alerts
- Table of contents
**Integrated services :**

- Disqus
- Duoshuo
- Google analytics
- Baidu analytics
- Gravatar
- Swiftype
- Facebook Insights
## Quick start ##

**Please read [user documentation](, it's short and useful to discover all features and possibilities of the theme, especially the [writing posts]( section**

##### For people who want to use the original version of Tranquilpeak without modifications (users)

1. Download the latest version ready for production use here : [hexo-theme-tranquilpeak-prod-1.7.1]
2. Follow [user documentation]( to install and configure the theme

##### For people who want to create their own version of tranquilpeak (developers)

1. Run `git clone`
2. Follow [developer documentation]( to edit and build the theme

## Demo ##

Check out Tranquilpeak theme in live : [hexo-theme-tranquilpeak demo](

## Showcase ##

I would like to create a showcase with all blogs that use Tranquilpeak, please, add your blog into.
**Click [here](,%20add%20my%20blog%20into%20the%20showcase:) to add your blog into the showcase.**

## Documentation ##

If it's your first time using Hexo, please check [Hexo official documentation](

##### For users

To install and configure the theme, consult the following documentation : [user documentation](

##### For developers

To understand the code, the workflow and edit the theme, consult the following documentation : [developer documentation](

## Contributing ##

All kinds of contributions (enhancements, new features, documentation & code improvements, issues & bugs reporting) are welcome.

Read [guidelines for contributing]( for more information.

## License ##

hexo-theme-tranquilpeak is released under the terms of the [GNU General Public License v3.0](

+ 161
- 0
themes/tranquilpeak/_config.yml View File

@@ -0,0 +1,161 @@
# Tranquilpeak
# Version : 1.7.1
# Author : Louis Barranqueiro

# I STRONGLY recommend you to use a CDN to speed up loading of pages.
# There is many free CDN like Cloudinary or you can also use indirectly
# by using services like Google Photos.

# If you want to store images yourself, please read this guidelines:
# For users, if you only use this theme, put your images directly in `source/assets/images` folder
# But if you want to add local images, you can put your images directly in `source/assets/images` folder
# For developpers, if you modify this theme, put your images in `source/_images` folder and
# use grunt task `build` to synchronize assets

# Image directory (default: images)
image_dir: assets/images

# Sidebar Configuration
# You can add groups of links and links much as you want
# You just have to respect the indentation : `groups of links` -> `link` -> `title, link, icon`
# E.g:
# -------------
# sidebar: # DON'T modify this variable name
# menu: # Name of your groups of links (changeable)
# home: # Name of your link (changeable)
# title: Home # Title of your link displayed
# url: / # URL of the link. If the URL is internal, domain name is not necessary
# icon: home # Name of the font awesome icon class without the `fa-`
# # Go to to find class name of icon
title: global.home
url: /
icon: home
title: global.tags
url: /all-tags
icon: bookmark
title: Help
url: /help
icon: question-circle
title: About
url: /about
icon: info-circle
title: Events
icon: calendar
title: Wiki
icon: university #wikipedia-w
title: Webmail
icon: envelope-square
title: Webchat
icon: wechat
title: global.archives
url: /all-archives
icon: archive
title: global.github
icon: github
title: global.twitter
icon: twitter
title: global.facebook
icon: facebook
title: global.mail
icon: envelope-o
title: global.rss
url: /atom.xml
icon: rss

# Header configuration
# The link at the right of the header is customizable
# You can add a link (as an icon) at the right of the header instead of the author's gravatar image or author's picture.
# By default, author's gravatar or author's picture is displayed if `icon` is empty
# DON'T edit `header`, `right_link`, `url`, `icon` and `class` variable name
# E.g to display a shortcut to open swiftype search window :
url: /#about
icon: info

# Author
# Your biography and your job is editable in each languages files in `languages` folder
location: Redbrick is DCU's Networking Society, Clubs and Societies Office, Dublin City University, Glasnevin, Dublin 9.
bio: Redbrick is DCU’s Computer Networking society. We host events for everything computing related this ranges from, how to setup your own website and storing your photos online to System Administration and Computer Programming Tutorials. We also host a number of services for our membership. <a href="/about">more</a>
# Your profile picture located in folder `source/_images/` (development)
# or in `source/assets/images/` (production)
picture: brick.png
# Your Twitter username without the @. E.g : `tranquilpeak`
twitter: redbrickdcu
# Your google plus profile id. E.g : `+Tranquilpeak` or `123812884128439`

# Customization
# Define the behavior of the sidebar
# 1: Display large sidebar on large screen, medium sidebar on medium screen and header bar on small screen
# and large sidebar is swiped
# 2: Display medium sidebar on large and medium screen and header bar on small screen and medium sidebar is swiped (default)
# 3: Display header bar on all screens and large sidebar is swiped
# 4: Display header bar on all screens and medium sidebar is swiped
sidebar_behavior: 1
# Hide sidebar on all article page to let article take full width to improve reading, and enjoy wide images and cover images. (true: enable, false: disable)
clear_reading: true
# Display thumbnail image of each post on index pages (false: disabled, true: enabled)
thumbnail_image: true
# Display thumbnail image at the right of title in index pages (`right`, `left` or `bottom`)
# Set this value to `right` if you have old posts to keep the old style on them
# and define `thumbnailImagePosition` on a post to overwrite this setting
thumbnail_image_position: right
# Automatically select the cover image or the first photo from the gallery of a post if there is no thumbnail image as the thumbnail image
# Set this value to `true` if you have old posts that use the cover image or the first photo as the thumbnail image
# and set `autoThumbnailImage` to `false` on a post to overwrite this setting
auto_thumbnail_image: true
# Your blog cover picture. I STRONGLY recommend you to use a CDN to speed up loading of pages.
# There is many free CDN like Cloudinary or you can also use indirectly
# by using services like Google Photos.
# Current image is on AWS S3 and delivered by AWS CloudFront.
# Otherwise put your image in folder `source/_images/` (development) or in `source/assets/images/` if you can't or don't want to build the theme,
# and use relative url : `your-image.png`
cover_image: cover.jpg
# Your favicon located in folder `source/_images/` (development) or in `source/assets/images/` (production)
favicon: brick.ico
# Display an image gallery at the end of a post which have photos variables (false: disabled, true: enabled)
image_gallery: true
# Pagination behavior of archive, category and tag pages (false: pagination disabled, true: pagination enabled)
archive_pagination: true
category_pagination: true
tag_pagination: true

# Your Google analystics web property ID : UA-XXXXX-X
# Your Facebook user ids used to connect your blog with your facebook user accounts (Facebook Insights). Separate ids with comma. e.g : 9830047,1003342
# Your Facebook app id used to connect your blog with your facebook app account (Facebook Insights). E.g : 9841307

+ 21
- 0
themes/tranquilpeak/bower.json View File

@@ -0,0 +1,21 @@
"name": "hexo-theme-tranquilpeak",
"version": "1.7.1",
"description": "A gorgeous responsive theme for Hexo blog framework",
"authors": [
"Louis Barranqueiro"
"license": "GNU General Public License v3.0",
"ignore": [
"dependencies": {
"fontawesome": "~4.3.0",
"jquery": "~2.1.3",
"fancybox": "~2.1.5"

+ 676
- 0
themes/tranquilpeak/docs/ View File

@@ -0,0 +1,676 @@
# Developer documentation #

This documentation will help you to understand Tranquilpeak Hexo theme code.

If you want to report a bug or ask a question, [create an issue](

## Summary ##

- [General](#general)
- [Requirements](#requirements)
- [Installation](#installation)1
- [Code style](#code-style)
* [Javascript code](#javascript-code)
* [ESLint configuration](#eslint-configuration)
* [Files/folders ignored by ESLint](#filesfolders-ignored-by-eslint)
* [Check code style](#check-code-style)
- [Code structure](#code-structure)
* [Views](#views)
* [Assets](#assets)
* [Stylesheets](#stylesheets)
* [Fonts](#fonts)
* [Images](#images)
* [Javascript](#javascript)
- [Build](#build)
* [NPM dependencies](#npm-dependencies)
* [Bower dependencies](#bower-dependencies)
* [Grunt tasks](#grunt-tasks)
* [Tasks structure](#tasks-structure)
* [Pipeline](#pipeline)
* [Config tasks](#config-tasks)
* [Register tasks](#register-tasks)
- [Running](#running)

## General ##

- **Author** : Louis Barranqueiro
- **Version** : 1.7.1
- **Compatibility** : Hexo 3.0.0 or later

## Requirements ##

1. **Node** : v0.10.35 or higher. Download [Node](
2. **Hexo CLI** : v0.1.4 or higher. Run `npm install hexo-cli -g`
3. **Grunt CLI** : v0.1.13 or higher. Run `npm install grunt-cli -g`