safe-concept-server

concept of project

each authorized user owns an encrypted file with application data.

server implements DDOS protection, code, SQL injections and provides file storage. one user - one encrypted file.

this concept supports the use of multiple applications.

it's assumed it will be used by standalone client applications that can storage user data in a single file. without application global or overlapped data.

project layers architecture

auth module layers architecture

project folder architecture

• server;
  • libs (common tools):
    • tool;
  • middleware:
    • CORS;
    • DDOS-traffic-analyzer;
    • HTTP-requests-analyzer;
    • DB-provider;
    • FS-provider;
  • guards:
    • guard;
  • routes:
    • module:
      • route-name (DB);
        • controller (works with request);
        • service (works with data);
        • caching service;
        • DB_adapter (multiple DB supporting);
        • DB_worker (SQL query sender);
      • route-name (FS);
        • controller;
        • service;
        • caching (only get_file);
        • FS_worker;

Project Roadmap

Deployment

1 set .env file:

cp .env.example .env

2 change vars in .env for your OS and preferences;

3 init DB for auth module (WIP)

4 set storage.index.json (WIP)

5 to run server (go needed):

./run-server.sh

5 to build server (go needed):

./build-server.sh

after building you can launch the binary file:

./build/server