No description
Find a file
2024-02-13 11:30:41 +01:00
backend Implementation details in backend readme 2024-02-13 09:54:47 +01:00
container Stripping server binary 2024-02-13 09:31:38 +01:00
frontend Package locks for npm 2024-02-12 13:13:17 +01:00
.containerignore Ignorefiles 2024-02-12 12:31:26 +01:00
.gitignore Option to export the production container to a tarball 2024-02-12 18:35:16 +01:00
BUILD.md Restructured build 2024-02-12 17:54:10 +01:00
Justfile Target update to avoid fail 2024-02-12 19:09:21 +01:00
LICENSE License 2024-02-12 12:29:47 +01:00
README.md Windows notes 2024-02-13 11:30:41 +01:00

TTime

Time Tracking Platform


Introduction

A time tracking platform that allows users to track their time and generate reports.

Build Instructions

The full build instruction is available here.
For developers specializing in the backend, there is documentation here.
For developers specializing in the frontend, there is documentation here.

Dependencies:

If you're on Fedora/Red Hat derivatives, this is as simple as:

sudo dnf install -y make golang nodejs podman just

Any Debian/Ubuntu-based distro:

sudo apt install -y make golang nodejs podman
sudo apt install -y just # For Ubuntu

Arch Linux & derivatives:

sudo pacman -S make go nodejs npm podman just

MacOS: (Requires Homebrew) (Untested)

brew install make go nodejs npm podman just

Windows:
Unfortunately, Windows Subsystem for Linux (WSL) is required for the build process. Running any form of containerized workload on windows is currently unsupported. More info here. From my understanding, WSL also requires virtualization extensions to be enabled in the BIOS, which is not always the case for all users.

It is possible to run the code on Windows, but this will be without the use of containers or any other build tools that are not available on Windows. You will also eventually need to install the database server, which will not be containerized.

My recommendation would be to make WSL your primary development environment if you are on Windows. This will drop you into an Ubuntu environment, in which you can follow the instructions above.

If you're still dead set on using windows ou will need the following:

With some grit and determination, you can get it to work. It's not recommended, but I (Imbus) will try to help you.