OwlBoard
/
backend
1
0
Fork 0
Code Issues 6 Pull Requests Packages Projects Releases Wiki Activity
The OwlBoard API Server & Hub Repo for all issues
174 Commits 1 Branch 3 Tags 5.7 MiB
TypeScript 58.8%
JavaScript 37.5%
HTML 3.1%
Dockerfile 0.6%
Go to file
Fred Boniface f7c20b3d99 Update logger config 
Signed-off-by: Fred Boniface <fred@fjla.uk>
 		2023-09-24 21:43:21 +01:00
.test-tools Run prettier 2023-08-26 00:38:26 +01:00
.vscode Run prettier 2023-08-26 00:38:26 +01:00
mail-templates Remove background from `html` to `table` 2023-09-24 20:50:27 +01:00
src Update logger config 2023-09-24 21:43:21 +01:00
test/utils Add test for issue fix: 2023-09-24 20:46:33 +01:00
.dockerignore pis (#12) 2023-05-06 21:54:49 +01:00
.eslintrc.js Run prettier 2023-08-26 00:38:26 +01:00
.gitignore Initial Push (v0.0.2) 2023-02-09 20:34:53 +00:00
.npmrc Working on staffStation.utils and added tests 2023-08-01 21:34:30 +01:00
Dockerfile Add dockerfilec omment 2023-08-30 20:28:46 +01:00
LICENSE Initial commit 2023-02-08 13:40:33 +00:00
README.md Run prettier 2023-08-26 00:38:26 +01:00
app.js Begin migration to Pino for logs 2023-09-24 21:35:36 +01:00
jest.config.js Run prettier 2023-08-26 00:38:26 +01:00
package-lock.json Begin migration to Pino for logs 2023-09-24 21:35:36 +01:00
package.json Begin migration to Pino for logs 2023-09-24 21:35:36 +01:00
tsconfig.json Fix tests for new output for estimated and actual times. Clientside can now directly display the value if it is a string, or if date should be displayed in suitable format. 2023-09-14 21:14:13 +01:00

README.md

OwlBoard

OwlBoard is both a backend API, and a frontend Arrival/Departure board webapp.

Powered by Node.JS and using the ldbs-json module, the OwlBoard API provides up to date train departure information for any station in the UK.

Build

To build the application with Docker, clone the repository and run docker build

API Endpoints:

API Documentation has been removed as it is now out of date. I do intent to re-write the documentation at a later date.

Configuration:

Configuration options are set through environment variables. These configuration options are shared with other programs in the OwlBoard ecosystem.

VAR DEFAULT REQUIRED PURPOSE
OWL_SRV_PORT 8460 NO Web Server Port
OWL_SRV_LISTEN 0.0.0.0 NO Web Server Listen Address
OWL_DB_USER owl NO Database Username
OWL_DB_PASS twittwoo NO Database Password - Do not leave as default in production
OWL_DB_NAME owlboard NO Database Name
OWL_DB_PORT 27017 NO Database Server Port
OWL_DB_HOST localhost NO Database Server Host
OWL_LDB_KEY YES National Rail LDBWS API Key
OWL_LDB_SVKEY NO National Rail LDBSVWS API Key
OWL_LDB_CORPUSUSER YES Network Rail NROD Username
OWL_LDB_CORPUSPASS YES Network Rail NROD Password
OWL_GIT_ISSUEBOT NO Gitea API Key for issue reporting
OWL_GIT_APIENDPOINT NO Gitea API Endpoint

In the case that OWL_LDB_SVKEY is not available, staff versions of departure board, etc. will not be available.

In the case that OWL_GIT_ISSUEBOT is not available, the 'Report Issue' page will not be able to POST data.

Database

OwlBoard uses MongoDB

The OwlBoard database is managed by the dbmanager application which will configure and maintain the database and should be run at least twice a day to ensure timetable data is up to date, see https://git.fjla.uk/owlboard/db-manager.