Skip to content

Improve Build and run experience with one command script #6982

Open

Description

@moshebeeri

Description of the issue

As I look readme file I see
cd ./dev/
rush build # Will build all the required packages.

rush rebuild # could be used to omit build cache.

rush bundle # Will prepare bundles.
rush package # Will build all webpack packages.
rush validate # Will validate all sources with typescript and generate d.ts files required for ts-node execution.
rush svelte-check # Optional. svelte files validation using svelte-check.
rush docker:build # Will build Docker containers for all applications in the local Docker environment.
rush docker:up # Will set up all the containers

I would expect one command ./dev/rush_buld.sh

Your environment

  • Version of Huly - Latest
  • Browser (and version) - N/A
  • Your operating system (and version) - N/A

Steps to reproduce

See readme.md

Expected behaviour

Tell us what should happen.

Actual behaviour

Tell us what happens instead (include screenshots or logs).
./dev/rush_buld.sh

Possible solutions

./dev/rush_buld.sh
#/bin/bash
cd ./dev/
rush build # Will build all the required packages.

rush rebuild # could be used to omit build cache.

rush bundle # Will prepare bundles.
rush package # Will build all webpack packages.
rush validate # Will validate all sources with typescript and generate d.ts files required for ts-node execution.
rush svelte-check # Optional. svelte files validation using svelte-check.
rush docker:build # Will build Docker containers for all applications in the local Docker environment.
rush docker:up # Will set up all the containers
cd ..
If you know how to fix the bug, please describe your solution here.

Activity

  1. kike49 commented on Oct 19, 2024

    @kike49

    We are expecting a single command (./dev/rush_buld.sh) that wraps all the individual Rush commands described in the README. Here's a possible solution: creating a bash script rush_build.sh that will execute all of these commands in sequence.

    1. Create the rush_build.sh file:

      • Navigate to the ./dev/ directory.
      • Create a new shell script file called rush_build.sh with the following command:
      touch rush_build.sh
    2. Edit the rush_build.sh file:

      • Open the file in a text editor and add the necessary commands to execute each Rush step in the desired order. Here’s an example of what your rush_build.sh script might look like:
      #!/bin/bash
      # This script will run the rush build process
      
      cd ./dev/
      
      # Build all the required packages
      rush build
      
      # Rebuild to omit cache (optional, uncomment if needed)
      # rush rebuild
      
      # Prepare bundles
      rush bundle
      
      # Build webpack packages
      rush package
      
      # Validate TypeScript and generate .d.ts files
      rush validate
      
      # Optional: validate svelte files using svelte-check
      rush svelte-check
      
      # Build Docker containers for all applications
      rush docker:build
      
      # Set up all containers
      rush docker:up
      
      # Navigate back to the original directory
      cd ..
    3. Make the script executable:

      • Run the following command to give the script execution permissions:
      chmod +x rush_build.sh
    4. Run the script:

      • Now you can run this script with the command:
      ./dev/rush_build.sh

    Notes:

    • The script will execute the sequence of commands as specified in the README, allowing you to run everything with a single command.
    • You can customize the script by commenting out any commands that aren't needed (e.g., the rush rebuild step, depending on whether you want to omit the build cache).
  2. MichaelUray commented on Oct 20, 2026

    @MichaelUray
    Contributor

    The repository now has scripts/build.sh (and scripts/fast-start.sh), which builds and starts the stack in one command, and README.md documents it; 'rush docker:build' also runs the needed build, bundle and package steps itself. It was checked against the current Platform-Collective develop code. If maintainers agree this covers the report, please consider closing.

  3. MichaelUray commented on Oct 20, 2026

    @MichaelUray
    Contributor

    @moshebeeri — based on the check described above, this looks resolved in the current code. Could you please close this issue if you agree? If you think it is not fixed yet, please describe what still goes wrong (steps, expected vs. actual behaviour), so it can be looked at again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions