Add a top-level run command to the "play with prototype"
All checks were successful
/ test (pull_request) Successful in 2m19s
All checks were successful
/ test (pull_request) Successful in 2m19s
It's very convenient for me to just stay in the top-level directory of a project. This change shows how to do that for `trunk`. I haven't figured out how to do it with `cargo test`, however. If you happen to know, feel free to edit.
This commit is contained in:
parent
b86f176151
commit
7dad623947
1 changed files with 1 additions and 0 deletions
|
@ -41,6 +41,7 @@ The latest prototype is in the folder `app-proto`. It includes both a user inter
|
||||||
2. Call `trunk serve --release` to build and serve the prototype
|
2. Call `trunk serve --release` to build and serve the prototype
|
||||||
* *The crates the prototype depends on will be downloaded and served automatically*
|
* *The crates the prototype depends on will be downloaded and served automatically*
|
||||||
* *For a faster build, at the expense of a much slower prototype, you can call `trunk serve` without the `--release` flag*
|
* *For a faster build, at the expense of a much slower prototype, you can call `trunk serve` without the `--release` flag*
|
||||||
|
* *If you want to run from the top level of the project, you can say `trunk --config app-proto serve [--release]`*
|
||||||
3. In a web browser, visit one of the URLs listed under the message `INFO 📡 server listening at:`
|
3. In a web browser, visit one of the URLs listed under the message `INFO 📡 server listening at:`
|
||||||
* *Touching any file in the `app-proto` folder will make Trunk rebuild and live-reload the prototype*
|
* *Touching any file in the `app-proto` folder will make Trunk rebuild and live-reload the prototype*
|
||||||
4. Press *ctrl+C* in the shell where Trunk is running to stop serving the prototype
|
4. Press *ctrl+C* in the shell where Trunk is running to stop serving the prototype
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue