No description
Find a file
2024-02-28 08:39:42 +01:00
backend Make use of the config 2024-02-28 08:39:42 +01:00
container Hardening the container 2024-02-20 19:44:26 +01:00
frontend Fixed double fetch 2024-02-20 18:41:12 +01:00
.containerignore Updating containerignore 2024-02-20 18:56:10 +01:00
.gitignore Gitignore the config file 2024-02-28 03:21:33 +01:00
BUILD.md Windows note fixed 2024-02-20 14:21:31 +01:00
Justfile Justfile targets adjusted for cleaning podman with podman-clean 2024-02-20 14:10:07 +01:00
LICENSE License 2024-02-12 12:29:47 +01:00
README.md Further windows notes related to WSL 2024-02-13 11:40:32 +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.

You should consult the WSL documentation, but for any recent version of windows, installation essentially boils down to running the following command in PowerShell as an administrator:

wsl --install

If you get any errors related to virtualization, you will need to enable virtualization in the BIOS. This is a common issue, and you can find a guide for your specific motherboard online. This is a one-time operation and will not affect your windows installation. This setting is usually called "VT-x" or "AMD-V" and is usually found in the CPU settings. If you can't find it, shoot me a message and I'll find it for you.

If you're still dead set on using a vanilla Windows environment, you 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.