Home

Welcome to the easyrequirements.txt wiki!

Here I will show you how to edit your file, to make it ready for production.

---

BAT FILE (for windows):

• The only thing that I ask is that the easyrequirements ascii art along with my name and the edition of the script, is not changed. Thank you.
• Change path to requirements on line 24. pip install -r /your/path/to/the/requirements If your requirements.txt file is in the same folder as the bat file, then your line 24 will look like pip install -r ./requirements.txt.
• From line 64 on, that is where you put your readme. Just insert it by line after the echo statement.
• On line 73, you can change the github link to your own github, or keep it the same.
• That's it! Just insert this program and your requirements.txt file wherever your program is, making user installation of your requirements just a little bit easier.

SH FILE (for linux and mac):

• The only thing that I ask is that the easyrequirements ascii art along with my name and the edition of the script, is not changed. Thank you.
• Change path to requirements on line 12. pip install -r /your/path/to/the/requirements If your requirements.txt file is in the same folder as the bat file, then your line 24 will look like pip install -r ./requirements.txt.
• This readme is just a little bit different due to the way bash scripting works. To change the readme, change lines 19-28 and also lines 40-49.
• Again you can change the github, or keep it the same on both lines 29 and 50.
• That's it! Just insert this program and your requirements.txt file wherever your program is, making user installation of your requirements just a little bit easier.

JS FILE (for anything {I guess lmao, nobody is gonna use this})

• The only thing that I ask is that the easyrequirements ascii art along with my name and the edition of the script, is not changed. Thank you.
• All you have to do is change the .env file, with the readme link, and the donation link.
• No idea if anybody is gonna use this code at all but there it is.