Write a deployment packaging script #113

Merged
glen merged 8 commits from Vectornaut/dyna3:deployment-packaging into main 2025-08-11 03:33:21 +00:00
Member

Write a packaging script to help automate deployment, and document the deployment process in README.md. The packaging script and the configuration files around it are based on the ones from the Vectornaut/dyna3:demo-summer-2025 branch.

Also, move run-examples.sh into the tools folder that we created for the packaging script.

  • @glen will test this PR by using it to deploy the latest prototype for our Show & Ask at the Illustrating Mathematics reunion workshop.
Write a packaging script to help automate deployment, and document the deployment process in `README.md`. The packaging script and the configuration files around it are based on the ones from the [`Vectornaut/dyna3:demo-summer-2025`](https://code.studioinfinity.org/Vectornaut/dyna3/src/branch/demo-summer-2025) branch. Also, move `run-examples.sh` into the tools folder that we created for the packaging script. - [x] @glen will test this PR by using it to deploy the latest prototype for our Show & Ask at the Illustrating Mathematics reunion workshop.
Vectornaut added 3 commits 2025-08-08 02:05:36 +00:00
The packaging script and the configuration files around it are based on
the ones from the

  `Vectornaut/dyna3:demo-summer-2025`

branch.
Make deployment script more like examples script
All checks were successful
/ test (pull_request) Successful in 3m33s
b1d5db2dc2
Owner

It appears the README instructions for executing the examples are outdated. This seems to me an appropriate PR in which to update them (since the run-examples.sh moved). Please add a commit to do so, thanks.

It appears the README instructions for executing the examples are outdated. This seems to me an appropriate PR in which to update them (since the run-examples.sh moved). Please add a commit to do so, thanks.
Vectornaut added 1 commit 2025-08-08 03:36:50 +00:00
Update the instructions for running the examples
All checks were successful
/ test (pull_request) Successful in 3m35s
707b5bf52f
Vectornaut added 2 commits 2025-08-08 03:47:29 +00:00
Author
Member

@glen wrote in #113 (comment):

It appears the README instructions for executing the examples are outdated. […] Please add a commit to do so, thanks.

Done in commits 707b5bf and d14c303. I also did a little formatting cleanup in commit 737e725.

@glen wrote in https://code.studioinfinity.org/StudioInfinity/dyna3/pulls/113#issuecomment-3212: > It appears the README instructions for executing the examples are outdated. […] Please add a commit to do so, thanks. Done in commits 707b5bf and d14c303. I also did a little formatting cleanup in commit 737e725.
Owner

Too much italics for optimum readability. I'd say go back to upright for the running text of the sub bullets. Thanks!

Too much italics for optimum readability. I'd say go back to upright for the running text of the sub bullets. Thanks!
Vectornaut added 1 commit 2025-08-08 19:36:57 +00:00
Switch README step notes from italic to roman
All checks were successful
/ test (pull_request) Successful in 3m39s
f979e2cbb3
Author
Member

@glen wrote in #113 (comment):

Too much italics for optimum readability. I'd say go back to upright for the running text of the sub bullets. Thanks!

Done in commit f979e2c. The time I have to work on this pull request before our Show & Ask is getting very limited, so I think we should prioritize finding and fixing deployment issues from here on out.

@glen wrote in https://code.studioinfinity.org/StudioInfinity/dyna3/pulls/113#issuecomment-3216: > Too much italics for optimum readability. I'd say go back to upright for the running text of the sub bullets. Thanks! Done in commit f979e2c. The time I have to work on this pull request before our Show & Ask is getting very limited, so I think we should prioritize finding and fixing deployment issues from here on out.
glen reviewed 2025-08-08 19:50:13 +00:00
README.md Outdated
@ -68,0 +75,4 @@
1. From the `app-proto` folder, call `trunk build --release`
- Building in [release mode](https://doc.rust-lang.org/cargo/reference/profiles.html#release) produces an executable which is smaller and often much faster, but harder to debug and more time-consuming to build
- If you want to stay in the top-level folder, you can call `trunk serve --config app-proto --release` from there instead
Owner

Should this be trunk build --config app-proto --release to be parallel with the main item, or do you need to use serve for some reason when you are working from the parent directory?

Should this be `trunk build --config app-proto --release` to be parallel with the main item, or do you need to use `serve` for some reason when you are working from the parent directory?
Author
Member

Yes, that should say build! Corrected in commit ef9055e.

Yes, that should say `build`! Corrected in commit ef9055e.
glen marked this conversation as resolved
Vectornaut added 1 commit 2025-08-08 19:54:06 +00:00
Correct a copying error
All checks were successful
/ test (pull_request) Successful in 3m33s
ef9055e2b8
Owner

Produced a correctly operational-when-deployed 0.3pre release, so merging.

Produced a correctly operational-when-deployed 0.3pre release, so merging.
glen merged commit af18a8e7d1 into main 2025-08-11 03:33:21 +00:00
Sign in to join this conversation.
No description provided.