Guides

Security and Updates

Usually, the Laravel versions and packages do go hand in hand with new features, to leverage the latest tech and code the framework has to offer, it is always a good idea to keep up to date with the framework, or at worst stay no more than one version behind.

Security Vulnerabilities

If you discover a security vulnerability within any codebase or server, please send an email to info@propay.co.za. All security vulnerabilities will be promptly addressed. It is your duty as an employee of Propay in the development & server space to report any security vulnerabilities to the company.

Laravel

Keeping Laravel updated to the latest versions does not only give you the latest and greatest feature set, but it also ensures you have the latest bug fixes and patches applied to the framework. Updating the framework usually comes with performance improvements, such as better load times and more efficient code.

Packages

Keep your packages updated to the latest versions, this is not just running composer update and committing the composer.lock file, you will have to test the entire system where all the packages have been used to make sure nothing has broken. Unit testing will help with this, and it is a key player in the security of the system.

“Outdated and insecure packages are the main reason most WordPress sites get hacked.”

Secrets & Env Values

NEVER commit usernames, passwords, secrets, API keys & hashes to a repository, although they offer extra security and private repository features, it is still a third-party provider that can get hacked and employees working on the code and system. Remember, even if you commit it and you remove it from the repository it is still in the history and version control of the source code.

If you accidentally commit any of these values, please let your team know immediately so that the keys can be rotated and any usernames, passwords, etc. can be changed. Best security practices say that keys, passwords, etc. should be rotated on a regular basis.

“Most of the time, data leaks are inside jobs.”

Edit this pageorReport an issue

Introduction

We are a small team of developers, which means every team member can bring something to the table and make a difference in the software we build and in the daily workings of our clients. Having standards and following best practices for any programming language is essential for any development team. This keeps consistency across all the systems. Usually the readme.md file in any system private or open source is always your friend, most of the info related to the system is documented in there.

Introduction

We created an open source package with our implementation of the [repository pattern](https://github.com/PropaySystems/laravel-base-repositories). This gives you a lot of boilerplate so you write less code. You will need to be disciplined to use the functions correctly and stick to your standards.