Instructions to use AJKADZ/PHI_CODER with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use AJKADZ/PHI_CODER with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf AJKADZ/PHI_CODER:Q4_K_M # Run inference directly in the terminal: llama cli -hf AJKADZ/PHI_CODER:Q4_K_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf AJKADZ/PHI_CODER:Q4_K_M # Run inference directly in the terminal: llama cli -hf AJKADZ/PHI_CODER:Q4_K_M
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf AJKADZ/PHI_CODER:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf AJKADZ/PHI_CODER:Q4_K_M
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf AJKADZ/PHI_CODER:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf AJKADZ/PHI_CODER:Q4_K_M
Use Docker
docker model run hf.co/AJKADZ/PHI_CODER:Q4_K_M
- LM Studio
- Jan
- Ollama
How to use AJKADZ/PHI_CODER with Ollama:
ollama run hf.co/AJKADZ/PHI_CODER:Q4_K_M
- Unsloth Desktop
- Docker Model Runner
How to use AJKADZ/PHI_CODER with Docker Model Runner:
docker model run hf.co/AJKADZ/PHI_CODER:Q4_K_M
- Lemonade
How to use AJKADZ/PHI_CODER with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull AJKADZ/PHI_CODER:Q4_K_M
Run and chat with the model
lemonade run user.PHI_CODER-Q4_K_M
List all available models
lemonade list
- Atomic Chat
|
Download phi-coder-hf/llama.cpp/ci/README.md from AJKADZ/PHI_CODER: direct link, hf CLI and curl.
- Browser
- Download file 2.29 kB
-
https://huggingface.co/AJKADZ/PHI_CODER/resolve/main/phi-coder-hf/llama.cpp/ci/README.md
- Command line
-
hf download hf://AJKADZ/PHI_CODER/phi-coder-hf/llama.cpp/ci/README.md
-
curl -L -o README.md https://huggingface.co/AJKADZ/PHI_CODER/resolve/main/phi-coder-hf/llama.cpp/ci/README.md
2.29 kB
| # CI | |
| In addition to [Github Actions](https://github.com/ggml-org/llama.cpp/actions) `llama.cpp` uses a custom CI framework: | |
| https://github.com/ggml-org/ci | |
| It monitors the `master` branch for new commits and runs the | |
| [ci/run.sh](https://github.com/ggml-org/llama.cpp/blob/master/ci/run.sh) script on dedicated cloud instances. This allows us | |
| to execute heavier workloads compared to just using Github Actions. Also with time, the cloud instances will be scaled | |
| to cover various hardware architectures, including GPU and Apple Silicon instances. | |
| Collaborators can optionally trigger the CI run by adding the `ggml-ci` keyword to their commit message. | |
| Only the branches of this repo are monitored for this keyword. | |
| It is a good practice, before publishing changes to execute the full CI locally on your machine: | |
| ```bash | |
| mkdir tmp | |
| # CPU-only build | |
| bash ./ci/run.sh ./tmp/results ./tmp/mnt | |
| # with CUDA support | |
| GG_BUILD_CUDA=1 bash ./ci/run.sh ./tmp/results ./tmp/mnt | |
| # with SYCL support | |
| source /opt/intel/oneapi/setvars.sh | |
| GG_BUILD_SYCL=1 bash ./ci/run.sh ./tmp/results ./tmp/mnt | |
| # with MUSA support | |
| GG_BUILD_MUSA=1 bash ./ci/run.sh ./tmp/results ./tmp/mnt | |
| ``` | |
| ## Running MUSA CI in a Docker Container | |
| Assuming `$PWD` is the root of the `llama.cpp` repository, follow these steps to set up and run MUSA CI in a Docker container: | |
| ### 1. Create a local directory to store cached models, configuration files and venv: | |
| ```bash | |
| mkdir -p $HOME/llama.cpp/ci-cache | |
| ``` | |
| ### 2. Create a local directory to store CI run results: | |
| ```bash | |
| mkdir -p $HOME/llama.cpp/ci-results | |
| ``` | |
| ### 3. Start a Docker container and run the CI: | |
| ```bash | |
| docker run --privileged -it \ | |
| -v $HOME/llama.cpp/ci-cache:/ci-cache \ | |
| -v $HOME/llama.cpp/ci-results:/ci-results \ | |
| -v $PWD:/ws -w /ws \ | |
| mthreads/musa:rc4.2.0-devel-ubuntu22.04-amd64 | |
| ``` | |
| Inside the container, execute the following commands: | |
| ```bash | |
| apt update -y && apt install -y bc cmake ccache git python3.10-venv time unzip wget | |
| git config --global --add safe.directory /ws | |
| GG_BUILD_MUSA=1 bash ./ci/run.sh /ci-results /ci-cache | |
| ``` | |
| This setup ensures that the CI runs within an isolated Docker environment while maintaining cached files and results across runs. | |