Linux aries.aptans.com 4.18.0-348.20.1.lve.1.el8.x86_64 #1 SMP Wed Mar 16 08:45:39 EDT 2022 x86_64
Apache
: 135.181.142.107 | : 172.69.7.46
Cant Read [ /etc/named.conf ]
7.4.33
aja
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
home /
aja /
public_html /
ead /
lib /
mustache /
[ HOME SHELL ]
Name
Size
Permission
Action
src
[ DIR ]
drwxr-xr-x
CONTRIBUTING.md
1.8
KB
-rw-r--r--
LICENSE
1.06
KB
-rw-r--r--
README.md
1.75
KB
-rw-r--r--
readme_moodle.txt
824
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : CONTRIBUTING.md
# Contributions welcome! ### Here's a quick guide: 1. [Fork the repo on GitHub](https://github.com/bobthecow/mustache.php). 2. Update submodules: `git submodule update --init` 3. Run the test suite. We only take pull requests with passing tests, and it's great to know that you have a clean slate. Make sure you have PHPUnit 3.5+, then run `phpunit` from the project directory. 4. Add tests for your change. Only refactoring and documentation changes require no new tests. If you are adding functionality or fixing a bug, add a test! 5. Make the tests pass. 6. Push your fork to GitHub and submit a pull request against the `dev` branch. ### You can do some things to increase the chance that your pull request is accepted the first time: * Submit one pull request per fix or feature. * To help with that, do all your work in a feature branch (e.g. `feature/my-alsome-feature`). * Follow the conventions you see used in the project. * Use `phpcs --standard=PSR2` to check your changes against the coding standard. * Write tests that fail without your code, and pass with it. * Don't bump version numbers. Those will be updated — per [semver](http://semver.org) — once your change is merged into `master`. * Update any documentation: docblocks, README, examples, etc. * ... Don't update the wiki until your change is merged and released, but make a note in your pull request so we don't forget. ### Mustache.php follows the PSR-* coding standards: * [PSR-0: Class and file naming conventions](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md) * [PSR-1: Basic coding standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-standard.md) * [PSR-2: Coding style guide](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md)
Close
