Add ddev config file #111

bmartinez287 · 2023-10-09T04:39:13Z

The Issue

This repo does not use a ddev file that requires one to install npm. I tried making my own a while back and ended up down a rabbit hole. It potentially adds a barrier to contrib.
Because ddev is already on my machine it would be nice to take advantage of it to among other things switch npm versions and have easy access to a database.

How This PR Solves The Issue

This PR adds the ddev config file. However, I ran into a few issues.

Network ddev_default created
Failed to get project(s): invalid app type: astro

If I set the project type to astro it will complain since it's not on the list and that makes sense I suppose but It made me think whether there should be a custom type or a generic type.

Additionally, I was trying to run ddev npm run dev and map the local HTTPs server port 4321 but when I tried it with web_extra_exposed_ports it did not work. It gave me a bad route error.

I might be missing some history on why some of these items are the way they are. I will look on Discord and see if I can find them.

bmartinez287 · 2023-10-09T04:57:32Z

After looking at some plugins I wonder if Astro dev settings should be part of a plugin such as vite and others.
https://github.com/tyler36/ddev-viteserve
The vite one is a good example. That might still require a custom project type or some sort of tag for a project base.

rfay

Thanks - The next thing to add is to update the README explaining how to use it.

You could also get just slightly fancier and change the nginx config to use astro as its upstream instead of php-fpm, and then everything would be on ports 80 and 443.

.ddev/config.yaml

rfay

This seems fine. If you wanted to automatlcally npm run dev you could do it with a web_extra_daemons stanza.

bmartinez287 · 2023-10-10T21:19:16Z

I'm looking into the nginx config to switch from php-fpm but I'm not sure if I found the right settings there.

Additionally, Astro runs Vite underhood so I figure maybe the Vite ddev add-on or running vite as a web_extra_exposed_ports would do it but so far I haven't been able to get HMR Hot module reloading working with Astro Vite implementation. I saw a few support posts on discord about some getting it to work but they are using a standard vite install and I think Astro does a wrapper which might complicate it a bit.

The dev.config file works well as it is if one just runs npm run build but it be nice to solve it for npm run dev as well

bmartinez287 · 2023-10-10T21:43:16Z

I get an astro.conf in /etc/supervisor/conf.d/astro.config after I do a ddev.ssh with the following settings.

[program:astro]
group=webextradaemons
command=bash -c "npm run dev || sleep 2"
directory=/var/www/html
autostart=false
autorestart=true
startretries=15
stdout_logfile=/var/tmp/logpipe
stdout_logfile_maxbytes=0
redirect_stderr=true

Which seems fine. Looking at this issue ddev/ddev#4872 but port 9998 or 9999 does not let me reach it it gives me a bad gateway.

I imagine this should be reachable http://ddev.com.ddev.site:9998/ and I thought that would give me the same output as npm run dev on a local environment. I must be missing a step since I got a bad gateway error.

bmartinez287 · 2023-10-13T00:10:57Z

time="2023-10-12T23:55:54Z" level=debug msg="'502 Bad Gateway' caused by: dial tcp 192.168.112.4:4321: connect: connection refused"
192.168.112.1 - - [12/Oct/2023:23:55:54 +0000] "GET /favicon.ico HTTP/2.0" 502 11 "-" "-" 51 "ddev-astrosite-web-4321-https@file" "http://ddev-ddev-astrosite-web:4321" 1ms

ddev logs --follow --time

bmartinez287 · 2023-10-13T20:49:35Z

Got it working, the issue was a missing -- that Atro Vite required to allow all hosts.
I added instructions to the README and updated the files.

rfay

Congrats on all the good work. Variety of suggestions, I haven't manually tested yet.

rfay · 2023-10-14T11:49:08Z

.ddev/config.yaml

@@ -0,0 +1,35 @@
+name: astrosite


Recommend just leaving this out if possible. It will then take the name of the directory it's in.

Suggested change

name: astrosite

rfay · 2023-10-14T11:49:53Z

.ddev/config.yaml

+# The extra -- is a Vite item
+# https://github.com/vitejs/vite/discussions/3396
+web_extra_daemons:
+  - name: astro-dev-deamon


Might as well spell it as expected.

Suggested change

- name: astro-dev-deamon

- name: astro-dev-daemon

Sounds good

.ddev/config.yaml

README.md

rfay

ddev npm run build gets

▶ src/pages/index.astro
node:internal/event_target:1033
  process.nextTick(() => { throw err; });

Since you're using web_extra_exposed_ports you shouldn't be telling people to hit http://127.0.0.1, should be named URL, for example https://ddev.com.ddev.site:4321 (which works)

But https://ddev.com.ddev.site:4321/blog gets me a 404.

The post-start hook shows By default it will be available at port 4321 - URL:4321, but there's no reason it can't show the full URL using ${DDEV_PRIMARY_URL}:4321

rfay · 2023-10-16T10:00:36Z

README.md

+DDev already has all the dependencies included.
+
+1. Run `ddev start && ddev npm install` set up the project’s dependencies.
+3. `npm run build` can be found at the base URL and `npm run dev` is found at URL:4321. Dev has Vite HMR(hot module reloading) among other features. The site will automatically refresh as you work on it, displaying errors in the relevant console (terminal or browser).


Suggested change

3. `npm run build` can be found at the base URL and `npm run dev` is found at URL:4321. Dev has Vite HMR(hot module reloading) among other features. The site will automatically refresh as you work on it, displaying errors in the relevant console (terminal or browser).

2. `ddev npm run build` can be found at the base URL and `ddev npm run dev` is found at URL:4321. Dev has Vite HMR(hot module reloading) among other features. The site will automatically refresh as you work on it, displaying errors in the relevant console (terminal or browser).

${DDEV_PRIMARY_URL}:4321 - I was looking for that variable for a while haha, I will work on that.

http://127.0.0.1/ is for the local setup without DDev in case they just want to run npm but maybe I can make that clearer I will double check.

I did not see that build error I will check on that one as well.

Thanks for the feedback.

bmartinez287 · 2023-10-16T19:43:40Z

I updated my OS to Sonoma, switched to Colima, and have been running into an odd issue where it gives me an operation not permitted.

I'm probably hitting an OS bug now 😑

That with ddev start && ddev npm cache clean --force && ddev npm install the fact one has to cache clean as sometimes it gets stuck in between.
More updates to follow.

bmartinez287 · 2023-10-16T20:06:40Z

DDev npm run build works well for the most part. But has that same error.

npm WARN tar TAR_ENTRY_ERROR EPERM: operation not permitted, open '/var/www/html/node_modules/@isaacs/cliui/node_modules/emoji-regex/package.json'
npm WARN tar TAR_ENTRY_ERROR EPERM: operation not permitted, open '/var/www/html/node_modules/timm/.github/workflows/run-tests.yml'
npm WARN tar TAR_ENTRY_ERROR EPERM: operation not permitted, open '/var/www/html/node_modules/tailwindcss/node_modules/postcss-selector-parser/dist/selectors/index.js'
npm WARN tar TAR_ENTRY_ERROR EPERM: operation not permitted, open '/var/www/html/node_modules/@jridgewell/trace-mapping/dist/types/sort.d.ts'
npm WARN tar TAR_ENTRY_ERROR EPERM: operation not permitted, open '/var/www/html/node_modules/pngjs/lib/packer.js'
npm WARN tar TAR_ENTRY_ERROR EPERM: operation not permitted, open '/var/www/html/node_modules/bottleneck/LICENSE'

rfay · 2023-10-16T20:27:18Z

Not sure what you were hitting there, especially if you had mutagen enabled. Can't tell much about what you were running against with Colima without knowing what Colima config you were using and whether you had mutagen enabled. However, note that Lima just had an update...

bmartinez287 · 2023-10-16T20:30:48Z

https://ddev.readthedocs.io/en/stable/users/install/docker-installation/#macos
I'm running the docs install but more specifically.
colima start --cpu 4 --memory 6 --disk 100 --vm-type=qemu --mount-type=sshfs --dns=1.1.1.1
I'm doing brew docker version 24.0.6 and brew colima version 0.5.6.

Yeah, I might have gone too close to the bleeding edge now. O well, it will work eventually hahaha.

rfay · 2023-10-16T20:35:35Z

Not sure how you can get permissions errors with that setup if using mutagen.

New limactl version (which makes a big difference) is

limactl version 0.18.0

bmartinez287 · 2023-10-16T20:38:07Z

Ups, I was not using mutagen. Thanks for adding that note.

bmartinez287 · 2023-10-16T21:01:51Z

It's working!!! and I think is ready.

To run it in ddev make sure to run ddev start && ddev npm install so the daemon won't crash the web container.

If it fails then run ddev npm cache clean --force && ddev npm install && ddev restart

Sometimes the npm cache will get stuck if one compiles it locally and then inside the container. Doing both creates chaos and requires a little more knowledge of the npm cache.

mattstein · 2023-10-19T15:37:15Z

README.md

@@ -65,7 +65,7 @@ All commands are run from the root of the project, from a terminal:

 DDev already has all the dependencies included.

-1. Run `ddev start && ddev npm install` set up the project’s dependencies.
+1. Run `ddev start && ddev npm cache clean --force  && ddev npm install ` set up the project’s dependencies.


Safe to get rid of the extra space unless that was important:

Suggested change

1. Run `ddev start && ddev npm cache clean --force && ddev npm install ` set up the project’s dependencies.

1. Run `ddev start && ddev npm cache clean --force && ddev npm install` set up the project’s dependencies.

mattstein · 2023-10-19T15:38:48Z

README.md

@@ -65,7 +65,7 @@ All commands are run from the root of the project, from a terminal:

 DDev already has all the dependencies included.


Not sure where “DDev” came from, but it should always be referred to as DDEV the product or ddev the command.

Suggested change

DDev already has all the dependencies included.

DDEV already has all the dependencies included.

mattstein · 2023-10-19T15:45:02Z

README.md

@@ -65,7 +65,7 @@ All commands are run from the root of the project, from a terminal:

 DDev already has all the dependencies included.

-1. Run `ddev start && ddev npm install` set up the project’s dependencies.
+1. Run `ddev start && ddev npm cache clean --force  && ddev npm install ` set up the project’s dependencies.
 3. `ddev npm run build` can be found at the base URL and `ddev npm run dev` is found at https://<projectname>.ddev.site:4321. Dev has Vite HMR(hot module reloading) among other features. The site will automatically refresh as you work on it, displaying errors in the relevant console (terminal or browser).


3 → 2, fix spacing, reword slightly for clarity:

Suggested change

3. `ddev npm run build` can be found at the base URL and `ddev npm run dev` is found at https://<projectname>.ddev.site:4321. Dev has Vite HMR(hot module reloading) among other features. The site will automatically refresh as you work on it, displaying errors in the relevant console (terminal or browser).

2. `ddev npm run build` can be found at the base URL and `ddev npm run dev` is found at https://<projectname>.ddev.site:4321. The dev server has Vite HMR (hot module reloading) among other features. The site will automatically refresh as you work on it, displaying errors in the relevant terminal or browser console.

What do you mean by ddev npm run build can be found at the base URL?

I know that running the build command generates a static version of the site into the dist/ directory, which you can run the preview command to serve, but the wording of this seems sort of ambiguous. Similarly with “ddev npm run dev is found at”—the command isn’t found at a browser address, but running it starts a server you can access from the browser at that address. I know you’re aware of this, but the wording leaves it unclear for someone figuring it out.

Yeah, I can see why it could be confusing. I updated the text to say.

ddev npm run build can be found at https://.ddev.site and ddev npm run dev is found at https://.ddev.site:4321.The dev server has Vite HMR (hot module reloading) among other features. The site will automatically refresh as you work on it, displaying errors in the relevant terminal or browser console.

mattstein · 2023-10-19T15:47:38Z

README.md

+
+To generate a static copy of the site, run `ddev npm run build`. The contents of the `dist/` folder are exactly what get [deployed to Cloudflare Pages](#build--deployment). You can preview locally by running `ddev npm run preview` or using a tool like [`serve`](https://www.npmjs.com/package/serve). 
+
+#### Without DDev setup


Suggested change

#### Without DDev setup

#### Setup Without DDEV

mattstein · 2023-10-19T15:48:48Z

README.md

-6. Run `npm run dev` to start Astro’s dev server.
-7. Visit the URL displayed in your terminal. (Probably `http://127.0.0.1:3000/`.) The site will automatically refresh as you work on it, displaying errors in the relevant console (terminal or browser).
+3. Run `npm run dev` to start Astro’s dev server.  If it fails then run `npm cache clean --force && npm install && npm run dev`. 
+4. Visit the URL displayed in your terminal. (Probably `http://localhost:4321/`.) The site will automatically refresh as you work on it, displaying errors in the relevant console (terminal or browser).


Suggested change

4. Visit the URL displayed in your terminal. (Probably `http://localhost:4321/`.) The site will automatically refresh as you work on it, displaying errors in the relevant console (terminal or browser).

4. Visit the URL displayed in your terminal. (Probably `http://localhost:4321/`.) The site will automatically refresh as you work on it, displaying errors in the relevant terminal or browser console.

mattstein · 2023-10-19T15:50:07Z

README.md


 To generate a static copy of the site, run `npm run build`. The contents of the `dist/` folder are exactly what get [deployed to Cloudflare Pages](#build--deployment). You can preview locally by running `npm run preview` or using a tool like [`serve`](https://www.npmjs.com/package/serve).

+
+#### Switching from without Ddev to with DDev local environment.


Use correct “DDEV”s and shorten:

Suggested change

#### Switching from without Ddev to with DDev local environment.

#### Switching from Without DDEV to With DDEV

mattstein · 2023-10-19T15:50:54Z

README.md

+
+#### Switching from without Ddev to with DDev local environment.
+
+Make sure to delete your node vendor folder everytime you switch and run npm install. The change in architecture can create odd issues otherwise.


Be specific, use backticks for command:

Suggested change

Make sure to delete your node vendor folder everytime you switch and run npm install. The change in architecture can create odd issues otherwise.

Make sure to delete your `node_modules/` directory and run `npm install`. The change in architecture can create odd issues otherwise.

bmartinez287 · 2023-10-19T17:34:05Z

I'm running into a few odd issues here among them.
ddev start && ddev npm install && ddev npm run build might be too long of an operation. It seems to get killed before it completes execution.

ddev start && ddev npm install works but for first-time setups, they would need the build folder to since that's where https://.ddev.site takes you.

Additionally, web_extra_daemons sometimes runs before ddev npm install and that breaks the build as it won't have anything to build upon. command: "sleep 3 && npm run dev -- --host" I added the sleep 3 to help with it since sometimes it is a race condition that could be mitigated by it. Is there another way to make ddev npm install run before web_extra_daemons?

The post-start hook would not do it because that has the same race condition issue.

rfay · 2023-10-19T19:32:55Z

If you're seeing killed check your Docker memory allocation.

bmartinez287 · 2023-10-27T15:44:41Z

This PR works but the daemon running before npm install has completed does concern me a bit. It fails if it can't find those files. I feel like I need a hook between pre-start and post-start so I can still do the npm install but it won't run the daemon until is over with it.

rfay · 2023-10-27T15:46:37Z

I'll try to take a look at this before long.

rfay · 2023-11-08T13:27:41Z

Sorry I lost track of this.

bmartinez287 · 2023-11-08T13:28:59Z

No worries, im sure you been pinned down after traveling fora while.

… in astro.

…osmicdreams.

rfay · 2023-11-08T14:06:57Z

Rebased

rfay · 2023-11-08T16:50:37Z

I'm seeing this kind of behavior:

> @ddev/[email protected] dev
> astro dev --host

  🚀  astro  v3.4.4 started in 554ms

  ┃ Local    http://localhost:4321/
  ┃ Network  http://172.27.0.2:4321/
             http://172.26.0.4:4321/

04:48:20 PM [content] Watching src/content/ for changes
04:48:21 PM [content] Types generated
04:48:21 PM [astro] update /.astro/types.d.ts
2023-11-08 16:48:22,015 INFO waiting for child_exit_monitor, php-fpm, nginx, mailpit, astro-dev-daemon to die
2023-11-08 16:48:25,023 INFO waiting for child_exit_monitor, php-fpm, nginx, mailpit, astro-dev-daemon to die
2023-11-08 16:48:26,030 WARN killing 'astro-dev-daemon' (2493) with SIGKILL
2023-11-08 16:48:27,031 INFO stopped: astro-dev-daemon (terminated by SIGKILL)
2023-11-08 16:48:27,033 INFO stopped: mailpit (exit status 0)
2023-11-08 16:48:27,068 INFO stopped: nginx (exit status 0)
[08-Nov-2023 16:48:27] NOTICE: Terminating ...
[08-Nov-2023 16:48:27] NOTICE: exiting, bye-bye!
2023-11-08 16:48:27,079 INFO stopped: php-fpm (exit status 0)
2023-11-08 16:48:27,079 INFO stopped: child_exit_monitor (terminated by SIGTERM)

Anyway, it comes up but I think astro dies soon, and then the whole web container gets brought down. I've seen this lately running npm run dev on the host a few times as well, it starts up and then dies.

Could you take a look and see what you see?

rfay · 2023-11-08T16:59:34Z

Never mind. I didn't follow the instructions.

rfay

Working great for me, thanks! Minor suggestion in README.

rfay · 2023-11-08T17:00:21Z

.ddev/config.yaml

+webserver_type: nginx-fpm
+additional_hostnames: []
+additional_fqdns: []
+performance_mode: mutagen # Important to avoid EPERM errors


I'd love to know what mode you were using and what docker provider you were using that gave you trouble.

README.md

Co-authored-by: Randy Fay <[email protected]>

bmartinez287 marked this pull request as draft October 9, 2023 04:57

rfay requested changes Oct 9, 2023

View reviewed changes

.ddev/config.yaml Outdated Show resolved Hide resolved

.ddev/config.yaml Outdated Show resolved Hide resolved

.ddev/config.yaml Outdated Show resolved Hide resolved

.ddev/config.yaml Outdated Show resolved Hide resolved

.ddev/config.yaml Outdated Show resolved Hide resolved

rfay approved these changes Oct 10, 2023

View reviewed changes

bmartinez287 marked this pull request as ready for review October 13, 2023 20:47

bmartinez287 requested a review from rfay October 13, 2023 20:47

rfay requested changes Oct 14, 2023

View reviewed changes

bmartinez287 requested a review from rfay October 15, 2023 21:18

rfay requested changes Oct 16, 2023

View reviewed changes

bmartinez287 requested a review from rfay October 16, 2023 21:02

mattstein requested changes Oct 19, 2023

View reviewed changes

bmartinez287 mentioned this pull request Oct 27, 2023

Blog post: Astro dev with DDEV article #116

Closed

Prototype v1 based on laravel template.

91bf715

bmartinez287 added 21 commits November 8, 2023 06:31

Added astro dev deamon.

e3221f6

Fixed typo.

6b5050e

Testing new settings to make Hot module reloading avaliable with vite…

131d888

… in astro.

Got it working, I will add instructions to the docs next. kuddos to c…

0c64d74

…osmicdreams.

test 2.

3a35d19

Added README instructions, plus cleanup config and added comments.

f56b088

Fix README.md

8537080

Fix README.md v2

136c247

Fix README.md v3

8abc405

Added changes as requested on PR review v1.

5c8754f

Added changes as requested on PR review v2.

28f4f86

Updated config based on feedback v2

45a4816

Updated config based on feedback ve

3993f7e

Testing new settings to avoid EPERM error.

4669b0b

Updated working version of the PR.

115c1a2

Updated working version of the PR v2.

60faaec

updated the docs with troubleshooting steps.

fa88a8c

Added README suggestions.

b272eab

Fix package-lock.json conflict.

6de4fbe

Updated README info.

c849d47

Updated README info v2.

a002105

rfay force-pushed the 20231009_ddev_config_file branch from 9a0e5ab to a002105 Compare November 8, 2023 14:06

rfay added 2 commits November 8, 2023 08:05

use node v20 as in config.yaml

4b8e5df

update package-lock.json

29ac25b

rfay approved these changes Nov 8, 2023

View reviewed changes

Update README.md

f9d2691

Co-authored-by: Randy Fay <[email protected]>

rfay merged commit a588d01 into ddev:main Nov 8, 2023
1 check passed

	3. `npm run build` can be found at the base URL and `npm run dev` is found at URL:4321. Dev has Vite HMR(hot module reloading) among other features. The site will automatically refresh as you work on it, displaying errors in the relevant console (terminal or browser).
	2. `ddev npm run build` can be found at the base URL and `ddev npm run dev` is found at URL:4321. Dev has Vite HMR(hot module reloading) among other features. The site will automatically refresh as you work on it, displaying errors in the relevant console (terminal or browser).

	1. Run `ddev start && ddev npm cache clean --force && ddev npm install ` set up the project’s dependencies.
	1. Run `ddev start && ddev npm cache clean --force && ddev npm install` set up the project’s dependencies.

		@@ -65,7 +65,7 @@ All commands are run from the root of the project, from a terminal:

		DDev already has all the dependencies included.

	3. `ddev npm run build` can be found at the base URL and `ddev npm run dev` is found at https://<projectname>.ddev.site:4321. Dev has Vite HMR(hot module reloading) among other features. The site will automatically refresh as you work on it, displaying errors in the relevant console (terminal or browser).
	2. `ddev npm run build` can be found at the base URL and `ddev npm run dev` is found at https://<projectname>.ddev.site:4321. The dev server has Vite HMR (hot module reloading) among other features. The site will automatically refresh as you work on it, displaying errors in the relevant terminal or browser console.


		To generate a static copy of the site, run `ddev npm run build`. The contents of the `dist/` folder are exactly what get [deployed to Cloudflare Pages](#build--deployment). You can preview locally by running `ddev npm run preview` or using a tool like [`serve`](https://www.npmjs.com/package/serve).

		#### Without DDev setup

	4. Visit the URL displayed in your terminal. (Probably `http://localhost:4321/`.) The site will automatically refresh as you work on it, displaying errors in the relevant console (terminal or browser).
	4. Visit the URL displayed in your terminal. (Probably `http://localhost:4321/`.) The site will automatically refresh as you work on it, displaying errors in the relevant terminal or browser console.


		To generate a static copy of the site, run `npm run build`. The contents of the `dist/` folder are exactly what get [deployed to Cloudflare Pages](#build--deployment). You can preview locally by running `npm run preview` or using a tool like [`serve`](https://www.npmjs.com/package/serve).


		#### Switching from without Ddev to with DDev local environment.


		#### Switching from without Ddev to with DDev local environment.

		Make sure to delete your node vendor folder everytime you switch and run npm install. The change in architecture can create odd issues otherwise.

	Make sure to delete your node vendor folder everytime you switch and run npm install. The change in architecture can create odd issues otherwise.
	Make sure to delete your `node_modules/` directory and run `npm install`. The change in architecture can create odd issues otherwise.

Add ddev config file #111

Add ddev config file #111

Conversation

bmartinez287 commented Oct 9, 2023

The Issue

How This PR Solves The Issue

bmartinez287 commented Oct 9, 2023

rfay left a comment

Choose a reason for hiding this comment

rfay left a comment

Choose a reason for hiding this comment

bmartinez287 commented Oct 10, 2023

bmartinez287 commented Oct 10, 2023

bmartinez287 commented Oct 13, 2023 • edited Loading

bmartinez287 commented Oct 13, 2023

rfay left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

rfay left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bmartinez287 commented Oct 16, 2023

bmartinez287 commented Oct 16, 2023 • edited Loading

rfay commented Oct 16, 2023

bmartinez287 commented Oct 16, 2023 • edited Loading

rfay commented Oct 16, 2023

bmartinez287 commented Oct 16, 2023

bmartinez287 commented Oct 16, 2023 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bmartinez287 Oct 19, 2023 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bmartinez287 commented Oct 19, 2023 • edited Loading

rfay commented Oct 19, 2023

bmartinez287 commented Oct 27, 2023

rfay commented Oct 27, 2023

rfay commented Nov 8, 2023

bmartinez287 commented Nov 8, 2023

rfay commented Nov 8, 2023

rfay commented Nov 8, 2023 • edited Loading

rfay commented Nov 8, 2023

rfay left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bmartinez287 commented Oct 13, 2023 •

edited

Loading

bmartinez287 commented Oct 16, 2023 •

edited

Loading

bmartinez287 commented Oct 16, 2023 •

edited

Loading

bmartinez287 commented Oct 16, 2023 •

edited

Loading

bmartinez287 Oct 19, 2023 •

edited

Loading

bmartinez287 commented Oct 19, 2023 •

edited

Loading

rfay commented Nov 8, 2023 •

edited

Loading