Write a deployment packaging script #113
No reviewers
Labels
No labels
bug
design
duplicate
enhancement
maintenance
prospective
question
regression
stub
todo
ui
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: StudioInfinity/dyna3#113
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "Vectornaut/dyna3:deployment-packaging"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 theVectornaut/dyna3:demo-summer-2025
branch.Also, move
run-examples.sh
into the tools folder that we created for the packaging script.run-examples.sh
into the tools folder 203e47397dIt 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.
@glen wrote in #113 (comment):
Done in commits
707b5bf
andd14c303
. I also did a little formatting cleanup in commit737e725
.Too much italics for optimum readability. I'd say go back to upright for the running text of the sub bullets. Thanks!
@glen wrote in #113 (comment):
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.@ -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
Should this be
trunk build --config app-proto --release
to be parallel with the main item, or do you need to useserve
for some reason when you are working from the parent directory?Yes, that should say
build
! Corrected in commitef9055e
.Produced a correctly operational-when-deployed 0.3pre release, so merging.