In production (actual use) we have the project based in our home dir, ~/ but that means our bin folder is taken, and other files (git, hidden scripts) sit in home. Instead, the project (and git repo) should be able to be placed anywere. On first run, it should create a link from the home dir, to wherever the control-panel.sh script was placed. That way, it's still easy to run from the default opened terminal, but the files don't rest in the home dir directly.
Another option is to just add the command to the user's bash profile (~/bash_profile?) so it can be run from any location (just like other linux commands like cd and wget etc). Then control-panel would be a command you type instead of running a script!
https://askubuntu.com/questions/297310/how-to-add-commands-to-terminal
In production (actual use) we have the project based in our home dir, ~/ but that means our bin folder is taken, and other files (git, hidden scripts) sit in home. Instead, the project (and git repo) should be able to be placed anywere. On first run, it should create a link from the home dir, to wherever the control-panel.sh script was placed. That way, it's still easy to run from the default opened terminal, but the files don't rest in the home dir directly.
Another option is to just add the command to the user's bash profile (~/bash_profile?) so it can be run from any location (just like other linux commands like
cdandwgetetc). Then control-panel would be a command you type instead of running a script! https://askubuntu.com/questions/297310/how-to-add-commands-to-terminal