Skip to content
This repository has been archived by the owner on Aug 6, 2020. It is now read-only.

Server Side Directory Structure

MattMoony edited this page Jan 14, 2020 · 4 revisions

Directory Structure (server-side)

If you have ever taken a look at the contents of our repository, you will have noticed the following filesystem structure:

website
|
|- lib
|  |- db.js
|  |- session.js
|  |- db.json
|  |- sessions.json
|- public
|  |- ...
|- res
|  |- maps
|  |  |- conf.json
|  |  |- ...
|  |- scss
|  |  |- ...
|- server.js
|- server.log

Note that some of the files listed above are not actually included in the repository, since they are either config- or log-files.


lib

The lib folder contains different Node modules and their configuration files - all of them essential to the server's proper functionality.

lib's files and their content are explained here

public

The public folder houses all files and folders that are part of the frontend (accessible via the web). Its contents are explained in Client Side - Directory Structure.

res

The res directory contains, as the name suggests, all resources, which are not necessarily accessible from the web, however.

res' files and their contents are explained here

res/maps

This is where all map files are saved to and loaded from. The res/maps directory itself can't be accessed from the frontend, its contents might be, however, depending on the client's privileges.

res/scss

This is were all uncompiled SCSS document are located.