Granted I didn’t spend long on it but what I was really after was more at the terminal level anyway. None of those options gave me exactly what I was looking for in terms of Ctrl+C stop behavior and output control. I started to address this with some of these Bash techniques, running multiple commands with &, trying fg to send to the foreground, grabbing process ids with $!, waiting on termination etc. Another issue is the stdout logs of the apps are no longer separated but mixed in and hard to follow. Starting the processes then isn’t the problem but stopping a specific one easily and cleanly (or all of them) may become one.
On Windows multiple console instances are launched and outside of Windows it all happens in the current one. There was one considerable difference however.
Osx iterm2 mac os#
Start-Process -FilePath 'pwsh' -WorkingDirectory $webPath -ArgumentList '-NoProfile -Command ng serve -o'īecause PowerShell Core is cross-platform the script technically worked on Mac OS as well. Start-Process -FilePath 'dotnet' -WorkingDirectory $somePath -ArgumentList 'run -debug' On Windows I had a PowerShell Core script with steps like the following. NET Core apps and an Angular website on Mac. Recently I had a need to start 3 related. However sometimes there may be a need to run the apps outside of containers locally or maybe when working with one or more non-containerized apps. If the apps are containerized then a Docker compose file, docker-compose up, docker-compose logs, and docker-compose down may be sufficient. Often multiple related apps need to be started in concert for a product and it’s convenient to automate that for local development.
0 kommentar(er)
