35447cc1c6
Hybrid approach of: - Always checking for legacy services for each workflow that involves installing new services, then disable and rename them. - Check for the rascsi group, as well as old rascsi.conf, rascsi_bridge, config dir and secret file inline whenever the script interacts with them, then rename them. - Check for the old self signed cert and key, as well as compiled protobuf libs, and delete them when the web ui is installed Also fixed: - the old manpage renaming script which should keep the old 'rascsi' names. - removed the ancient apache cleanup, since it's been over 2 years now since the PHP webapp was deprecated. - general purpose stop/disable/status functions for systemd services - general purpose deleteFile function - default to half of the max no. of cores for compiling - use the SKIP_PACKAGES flag in more functions - introduce a SKIP_MAKE_CLEAN flag |
||
|---|---|---|
| .github | ||
| cpp | ||
| doc | ||
| docker | ||
| hw | ||
| python | ||
| _config.yml | ||
| .dockerignore | ||
| .gitignore | ||
| easyinstall.sh | ||
| LICENSE | ||
| README.md | ||
What is PiSCSI?
PiSCSI is a virtual SCSI device emulator that runs on a Raspberry Pi. It runs in userspace, and can emulate several SCSI devices at one time. There is a control interface to attach / detach drives during runtime, as well as insert and eject removable media. This project is aimed at users of vintage Macintosh and Atari computers and more (see compatibility list) from the 1980's and 1990's.
Please check out the full story with much more detail on the wiki!
How do I contribute?
PiSCSI is using the Gitflow Workflow. A quick overview:
- The master branch should always reflect the contents of the last stable release
- The develop branch should contain the latest tested & approved updates. Pull requests should be used to merge changes into develop.
- The rest of the feature branches are for developing new features
- A tag will be created for each "release". The releases will be named .. where the release number is incremented for each subsequent release tagged in the same calendar month. The first release of the month of January 2021 is called "21.01.01", the second one in the same month "21.01.02" and so on.
Typically, releases will only be planned every few months.
When you are ready to contribute code to PiSCSI, follow the GitHub Forking and Pull Request workflow to create your own fork where you can make changes, and then contribute it back to the project. Please remember to always make Pull Requests against the develop branch.
If you want to add a new translation, or improve upon an existing one, please follow the instructions in the Web Interface README. Once the translation is complete, please use the same workflow as above to contribute it to the project.
GitHub Sponsors
Thank you to all of the GitHub sponsors who support the development community!
Special thank you to the Gold level sponsors!
Special thank you to the Silver level sponsors!
- @stinkerton18
- @hsiboy
- @pendleton115
- @Teufelhunden-0311
- Private sponsor ;]