Download the PHP package conceptte/testcrm without Composer
On this page you can find all versions of the php package conceptte/testcrm. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download conceptte/testcrm
More information about conceptte/testcrm
Files in conceptte/testcrm
Package testcrm
Short Description MiniCRM extension for Nette Framework (test example)
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package testcrm
MiniCRM - Test exersise
Journey
During the development of this package, I focused on creating a clean and modular architecture that can be easily integrated into any Nette-based application. I wanted to demonstrate best practices in Nette development, such as using extensions, presenters, and repositories to keep the code organized and maintainable.
I went throwgh such opics as:
- Nette extensions
- configuration
- bootstrap and services registration
- Dependency injection
- services registration and usage
- constructor injection
- Attributes for DI
- Routing for clean URLs
- route definitions
- Presenters
- parameters injection
- persistence parameters
- forms
- reusable components
- redraw and snippets
- Form handling
- Latte basics
- templates and layouts
- blocks and snippets
- Database interactions with repositories
- Explorer
- API design for JSON endpoints
- Security practices (CSRF, SQL injection prevention, XSS protection)
About the app
This package is built as a Nette extension, not as code mixed into the host app. That gives a few clear benefits:
- Host project only registers extension and routes.
- logic is in one place, not spread in many app files.
- host app can replace services by interface without editing core package code.
Main gap of extension in current version:
- (
fixed by custom copying assets files) Asset pipeline is limited: styles are kept in Latte layout blocks, not in fully separate built assets. - Sorting and filtering is basic, no complex queries or UI for that.
- No rate limiting or other protections for API endpoints.
- Error handling is basic, just showing messages without logging or detailed responses.
- No tests included, so it's not covered for edge cases or regressions.
Installation (Fast dockerized setup:)
I recomend to use the dockerized setup for quick testing. It includes a simple host app with the extension installed and configured, so you can see it in action right away. You can find it here: https://github.com/conceptte/testcrm-host.git
-
Install
-
Register in config:
-
Add routes in
app/Core/RouterFactory.php: -
Add assets to
www/assets(temporary solution, should be improved in future): - Create and seed database:
Basic simple structure:
Configuration
Extension configuration is done in config/minicrm.php
I decided to use PHP for configuration instead of NEON because it allows for more flexibility
And Nette supports it :
src/MiniCRMExtension.php:
You can easily swap out implementations or use real classes without needing a separate DI container configuration.
Routes:
Router is defined in src/Routing/RouterFactory.php. It makkes group of routes for the app and API.
Group of Frontend routes:
/minicrm/customers- Customer list page (search, filter, sort)/minicrm/customers/{public_id}- Customer details page (activities and history)/minicrm/customers/{public_id}/activity/{id}- Activity page (view details and comments)
API routes group:
/minicrm/api/v1/ping- API to check if the service is alive/minicrm/api/v1/customers- API to get customer data as JSON/minicrm/api/v1/customers/{public_id}- API to get single customer details as JSON
Database tables
schema.sql defines tables:
customers- stores customer infocustomer_activities- stores customer activitiesactivity_comments- stores comments on activities
Foreign keys and indexes are set for performance and data integrity.
Presenters
I investigated and used native Nette functionality like:
- forms for comment add
- snippets for small page updates
- pagination for long lists
- AJAX with Naja for no full page reload
Presenters use repository services, pagination control as dependencies injected by Nette DI container.
Repository layer
They provide methods to get data from the database and are used by presenters and API endpoints. Registered as services in extension config, so they can be injected and swapped if needed.
API
Get customers as JSON:
Response includes customer list and meta info:
Get single customer details:
Response includes customer info and some metadata:
Safety
Used Nette's built-in features to protect against common web vulnerabilities:
- CSRF attacks - forms have protection tokens
- SQL injection - database uses safe queries
- XSS - text is automatically escaped
- Rate limiting - N/A (not implemented yet, but can be added)
