34 lines
993 B
Markdown
34 lines
993 B
Markdown
|
---
|
||
|
title: Developing with Quartz
|
||
|
draft: false
|
||
|
date: 2025-01-17
|
||
|
---
|
||
|
|
||
|
This container is also good for quickly developing components for Quartz. It is a good way to test things out without having to install anything on your local machine, and a simple `make run` -> `ctrl-c` -> `up arrow` -> `enter` is all you need to see your changes.
|
||
|
|
||
|
I keep all of my projects in `~/Repositories`, so I would do this:
|
||
|
|
||
|
Link my primary development folder to the container repo's source folder:
|
||
|
```bash
|
||
|
cd ~/Repositories
|
||
|
git clone git@git.modernleft.org:gravityfargo/quartz-docker.git
|
||
|
git clone git@github.com:jackyzha0/quartz.git
|
||
|
```
|
||
|
|
||
|
Then mount the quartz directory to the development docker-compose file:
|
||
|
```yaml
|
||
|
volumes:
|
||
|
- ~/Repositories/quartz:/quartz/src
|
||
|
```
|
||
|
Then, you can run the container with the following command:
|
||
|
```bash
|
||
|
cd ~/Repositories/quartz-docker
|
||
|
make run
|
||
|
```
|
||
|
|
||
|
If 200+ files are claiming to be modified, you may need to disable filemode checking:
|
||
|
|
||
|
```bash
|
||
|
git config core.fileMode false
|
||
|
```
|