hfs

This file is mostly aimed to developers.

Building instructions

1. Install Node.js 18+
2. Install Typescript: launch npm -g i typescript
3. Launch npm run build-all in the root

At this stage you have a javascript output. For binary files you’ll also have to npm run dist-bin.

You could instead run dist to run both build-all & dist-bin.

Dev environment

1. npm install
2. npm run watch-server-proxied and leave it running. It will serve server stuff plus will proxy frontend and admin files.
3. npm run start-frontend and leave it running. It will serve on port 3005.
4. npm run start-admin and leave it running. It will serve on port 3006

If you don’t want this proxying version, you can use npm run watch-server but after both frontend and admin have been built, so their files are available in dist folder.

Tests

To run tests

• npm run build-all
• npm run server-for-test and leave it running.
• npm test

Alternatively you can run a development server, just be sure to load config from tests folder.

File organization

The project is roughly divided in Server + Frontend + Admin, where Frontend is a web interface intended to access shared files, while Admin is the web interface for configuration/administration.
Server lies in the root of the project, with its “src” folder, while Frontend and Admin are inside folders “frontend” and “admin” respectively, with their “src” folder within.

Additionally, you have the following folders:

• mui-grid-form: a lib used by Admin to easily build forms
• plugins: a collection of plugins that are pre-installed
• shared: code shared between Frontend and Admin
• tests: automated tests with related resources

Known problems

• vite’s proxying server (but also CRA’s) doesn’t play nicely with SSE, leaving sockets open

Guidelines

• For strings, I’m using double-quotes for text that’s read by the user, and single-quotes elsewhere. Backticks can be any.
• All objects that go in yaml should use snake_case.
  • Reason: we want something that is both easy for the user and maps directly in our code. Spaces and kebab-case don’t play well with javascript and camel is less readable for the user.
• API names should start with get_ if and only if they provide information without making changes.
• All parameters that contain a uri should have a name that starts with uri.
• React parts don’t use JSX. I used JSX for a couple of years before deciding that it is not good enough to pay the price of using an extra language that is also necessary to switched in and out multiple times when stuff is nested.

Project design

• At the moment the admin-panel was designed to be completely separated from the “user” frontend to keep the latter smaller and to allow alternative frontends creation without having to deal with the complexity of the admin-panel.

  Of course this comes with a price to pay on the programmer’s side, more work to do.

This site is open source. Improve this page.