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
Copy file name to clipboardExpand all lines: README.md
+14-9Lines changed: 14 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,16 @@
2
2
3
3
## Welcome
4
4
5
-
Setting up a development machine is a time-consuming and error-prone process. Programmer's System eliminates these issues by providing a light weight, automated, configurable solution to install your software ecosystems in Linux/Mac enviroments.
5
+
Setting up a development machine is a time-consuming and error-prone process. Programmer's System eliminates these issues by providing a light weight, automated, configurable solution to install industry standard software ecosystems in Linux/Mac enviroments.
6
+
7
+
Design Objective: The primary goal of this project is to maintain simplicity, grounded in the philosophy that it's built on a foundation of "just scripts." For a comprehensive overview, please refer to the [development guide](www.google.com). In essence, Programmer's System enables the seamless addition of Linux/Mac distributions with a focus on stability. Each distribution requires an initialization script for core packages and a package configuration file (requirements.txt format). Once configured, all scripts are neatly organized in distinct "ecosystem" folders, allowing users to customize their installation by commenting out specific packages. For example, if a user prefers Pipenv over Poetry in the "Python" ecosystem, they can easily modify their preferences, making sure to pass in `--python` when running.
8
+
9
+
Each package is encapsulated within a dedicated bash script, and a set of exposed bash functions facilitate package installation checks and the utilization of a shared script across all distributions. Explore the "ubuntu" directory for insights into the requirements.txt and "-core-" scripts, showcasing how ecosystems contain targeted and focused installation code within clearly defined folders and supporting script files. To ensure independence and code sharing, accessible bash functions are integrated into the install script. The system operates by executing scripts dedicated to installing individual packages, providing a streamlined and efficient provisioning mechanism. The code that powers the system is called sys.sh.
10
+
6
11
7
12
## Ecosystems
8
13
9
-
Utilizing the traditional **requirements.txt** configuration style, you can effortlessly define the packages to be included in your distribution. Afterward, the command-line interface (CLI) is run used to do the rest:
14
+
Utilizing the traditional *requirements.txt* configuration style, you can effortlessly define the packages to be included in your distribution's folder. Afterward, the command-line interface (CLI) is run used to do the rest:
0 commit comments