refactor!: new code structure and switched to fastapi (#1)

* Initial Setup, cleaning needed before merging to main

* refactor!: better code structure

* note things are current broken need to fix them later

---------

Co-authored-by: lbojo006 <luisbojorquezgoal@gmail.com>

Author: mingzezh

.gitignore

@@ -0,0 +1,8 @@
+__pycache__/
+
+.venv/
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+
+daqserver.egg-info/

.python-version

@@ -0,0 +1 @@
+3.14

README.md

@@ -1,2 +1,53 @@
 # daqserver
-The main DAQ server repo
+
+The main DAQ server repo.
+
+## Running this project
+
+1. Download the command [`uv`](https://docs.astral.sh/uv/getting-started/installation/) to your computer
+2. Download [`git`](https://git-scm.com/install/) command to your computer
+3. Clone the project `git clone https://github.com/Highlander-Space-Program/daqserver.git`
+4. Get into the source code `cd daqserver`
+5. Run the project `uv run server`
+
+You don't need to download any Python for this, `uv` will download the right
+version and install all of the packages for you.
+
+## Development
+
+If you are going to add a new package to the python code, use `uv add
+package-name`. When you are committing code, I recommend following the [git
+commit conventions](https://www.conventionalcommits.org/en/v1.0.0/). For this
+project, I don't want anyone to directly push code to the `main` branch, unless
+you are doing a quick bugfix or fixing a typo. What you are going to do is push
+your local branch to this remote repository, and then create a pull request
+that is going to merge into the `main` branch. The DAQ lead or DAQ SE will look
+over your code in the pull request. If it is good, we will merge your code to
+the `main` branch, and if it is not good, we will ask you to make some changes.
+The idea here is that we want to keep `main` branch stable and not breaking.
+This means that you need to always create a new branch whenever you started
+working on your code.
+
+## I am confused
+
+This section here shows you how to navigate and use the codebase. If you have
+trouble with creating a pull request or how to use `git` you should try looking
+for a quick Youtube Tutorial or try asking ChatGPT, and then learn how to solve
+ur `git` problem, so you won't have to deal with it again later in the future.
+
+Under some directories like [`scripts`](./scripts) and [`server`](./server),
+you may find another `README.md` file. Inside of these `README.md` files, you
+will find guides and descriptions that will help you with navigating around the
+codebase. Don't afraid to ping the DAQ lead or the DAQ SE for help. Trying to
+figure out how to work with a new codebase yourself is difficult. When you are
+assigned a task for this project, you are expected to know a little bit of
+Python and also a little bit of `git`. Please don't ever use `git push --force`
+or `git push --force-with-lease` if you have no idea what you are doing.
+
+For those of you who already know a little bit about Python, it's a good idea
+to follow the [`PEP-8`](https://peps.python.org/pep-0008/) styling guide when
+adding your code to the project. If you want to challenge yourself a bit more
+(and I would be really happy if you do), try to make sure that everything you
+wrote is [type hinted](https://peps.python.org/pep-0484/) and tested through
+`pytest` (yes this means I would like you to write some unit tests for your
+code whenever possible).

labjack_channels.json

@@ -0,0 +1,28 @@
+[
+    {
+        "Type": "AIN",
+        "AIN": "AIN48",
+        "NegativeAIN": "AIN56",
+        "SensorType": "LoadCell",
+        "Differential": true,
+        "Bank": null,
+        "CB37_Index": null
+    },
+    {
+        "Type": "AIN",
+        "AIN": "AIN50",
+        "SensorType": "Pressure",
+        "Differential": false,
+        "Bank": "X3",
+        "CB37_Index": 2
+    },
+    {
+        "Type": "AIN",
+        "AIN": "AIN52",
+        "NegativeAIN": "AIN60",
+        "SensorType": "Thermocouple",
+        "Differential": true,
+        "Bank": "X3",
+        "CB37_Index": 4
+    }
+]

pyproject.toml

@@ -0,0 +1,43 @@
+[project]
+name = "daqserver"
+version = "0.1.0"
+description = "The big daq server"
+readme = "README.md"
+requires-python = ">=3.14"
+dependencies = [
+    "fastapi[standard]>=0.135.1",
+    "labjack-ljm>=1.23.0",
+    "rich>=14.3.3",
+    "websockets>=16.0",
+]
+
+[tool.uv]
+package = true
+
+[project.scripts]
+server = "server.__main__:main"
+
+[tool.setuptools.packages.find]
+include = ["server*"]
+
+[tool.pyright]
+venvPath = "."
+venv = ".venv"
+
+[tool.ruff]
+line-length = 82
+
+[tool.ruff.format]
+docstring-code-format = true
+docstring-code-line-length = 80
+
+# [tool.ruff.lint]
+# # Add the `line-too-long` rule to the enforced rule set.
+# extend-select = ["E501"]
+
+[dependency-groups]
+dev = [
+    "mypy>=1.19.1",
+    "pathspec>=1.0.4",
+    "pytest>=9.0.2",
+]

scripts/README.md

@@ -0,0 +1,38 @@
+# Scripts
+
+<!-- filetree start -->
+
+```text
+daqserver
+├── scripts (You are here)
+└── server
+    ├── streaming
+    └── web
+        ├── static
+        │   ├── css
+        │   └── js
+        └── templates
+```
+
+<!-- filetree end -->
+
+## About scripts
+
+This directory contains all of the scripts that are going to help you
+throughout the development of this project. If you have other scripts that you
+want to add to here, feel free to do so. Make sure you have documented the
+scripts that you have added at the top of the script file so people know what's
+going on in the script and how to use it.
+
+Having the script be written in the Python language is preferred. Running the
+Python scripts is usually just `uv run scripts/script_name.py`, and this
+ensures cross platform compatibility (People using MacOS might not be able to
+use a `batch` script). If you have a good reason to use batch like creating
+some sort of installer for Windows users then feel free to use batch.
+
+## How to use the scripts
+
+If the script is written in Python (files that ends with `.py`), then you can
+should be able to run it using `uv run scripts/script_name.py` where you have
+to replace the `script_name` with the actual script's name. Please open the
+script file that you are running for documentation about how to use it.