You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today the brew install proton only grabs the binary file and put in a path.
then I run proton server start in any folder, it will generate config files and data/log files in current folders.
I may want to run proton install to install proton with system folders. Just like when I homebrew Grafana, MySQL or PostgreSQL. No matter where I start the command, the folders are fixed and I can reuse/tune the config file.
But it's odd to run brew install proton first then sudo proton install.
The key goal of homebrew is to handle such case, not just binary file, but also config/data/logs
Today the
brew install proton
only grabs the binary file and put in a path.then I run
proton server start
in any folder, it will generate config files and data/log files in current folders.I may want to run
proton install
to install proton with system folders. Just like when I homebrew Grafana, MySQL or PostgreSQL. No matter where I start the command, the folders are fixed and I can reuse/tune the config file.But it's odd to run
brew install proton
first thensudo proton install
.The key goal of homebrew is to handle such case, not just binary file, but also config/data/logs
You may want to do something similar as https://github.com/timeplus-io/proton/blob/develop/programs/install/Install.cpp in the homebrew way.
The text was updated successfully, but these errors were encountered: