It'd be cool if I don't need to create .mps directory and clone a password-repo myself.
The tool should do it for me. Maybe just ask user for a path (with an option to use the default one) and a repo URL.
It'd be cool if I don't need to create `.mps` directory and `clone` a password-repo myself.
The tool should do it for me. Maybe just ask user for a path (with an option to use the default one) and a repo URL.
Also, it can create a config file for me and set MPS_HOME there
This way, there would be only 2 initialization steps instead of 5:
Also, it can create a config file for me and set `MPS_HOME` there
This way, there would be only 2 initialization steps instead of 5:
@rozetko now you can just run `mps init` withour requirement to set all other steps
https://code.corpglory.net/corpglory/mps/src/commit/9da8c60340b8d8f43a2e5cadf7ec9a7b69d79173/README.md#installation
What do you think, is it better now?
It'd be cool if I don't need to create
.mpsdirectory andclonea password-repo myself.The tool should do it for me. Maybe just ask user for a path (with an option to use the default one) and a repo URL.
Also, it can create a config file for me and set
MPS_HOMEthereThis way, there would be only 2 initialization steps instead of 5:
Automatic initializationto Feature: Automatic initialization 3 months ago@rozetko now you can just run
mps initwithour requirement to set all other steps9da8c60340/README.md (installation)What do you think, is it better now?