Creme is a free/open-source Customer Relationship Management software developed by Hybird (www.hybird.org).
It is designed with an entities/relationships architecture, and is highly configurable, which allows
adapting Creme to many workflows.
It provides apps (i.e. modules) to manage:
- Contacts & organisations.
- Documents & folders.
- Activities (meetings, phone calls, tasks...) with a calendar.
- Products & services.
- Invoices, quotes, sales orders & credit notes.
- Opportunities.
- Commercial actions.
- Email campaigns.
- Reports.
- Tickets.
- Alerts, todos & memos.
- Geolocation.
- ...
Lots of aspects can be configured through a graphical interface :
- Detailed views for entities are built from blocks ; you can configure which blocks are
displayed, you can create your own the blocks (chose the fields which are used)...
- You can configure the columns of the list views (columns can be related to fields, custom-fields,
relationships...), and filter the lines with powerful rules.
- You can create your custom-fields, or hide existing fields.
- You can choose which fields of forms are used, and group them like you want.
- You can create your own types of relationship, adapted to your business.
- ...
Creme has powerful tools to filter, search or import data. it provides a credential system with
some cool features (teams, allow/forbid entities from a filter on fields/relationships, ...).
If you have very specific needs, Creme can also be used as a CRM framework to code your own CRM.
Creme is coded in Python, and uses the Django web framework (http://www.djangoproject.com/) and
the JQuery javascript library (http://jquery.com/).
You can find more information on Creme on its official website: http://cremecrm.com/
You can ask your questions in our forum: https://www.cremecrm.com/forum/index.php
(there is an english section)
### Current translations
- English (could probably be improved)
- French
### Recommendations:
It's recommended to use a database engine which supports transactions :
- PostGreSQL is probably the best choice for databases with 100,000+ entities.
- SQLite support is principally done for developers, but it remains a solution
for small databases (e.g. a use as mono-user app with the server running of your computer).
You probably should use 'virtualenv' (for an upgrade from Creme 2.4, you should create a new
virtual env, in order to keep the old one working).
### Dependencies
- Python 3.8+
- MySQL 8+ (or MariaDB 10.4+) or PostGreSQL 12+ (or SQLite which is included with Python)
- A web server compatible with Python, like Apache 2.4
- Redis 3+
- These Python packages :
(exact versions of Python packages are indicated in the 'setup.cfg' file)
- Mandatory :
- Django
- redis
- python-dateutil
- cryptography
- bleach
- Pillow
- django-formtools
- xlrd (to import contacts, organisations, activities, tickets... from xls files)
- xlwt (to export all types of entities -- like contacts or organisations -- as xls files)
- csscompressor
- rJSmin
- Optional :
- creme.billing :
If you want PDF export, you can use :
- xhtml2pdf (default)
- weasyprint (easy to install on Linux ; harder on Windows)
- you can also use the binary "pdflatex" (Ubuntu package 'texlive-latex-base').
Installation with 'pip':
- You should probably use "virtualenv".
- To install Creme itself :
- You can just install from pyPI: 'pip install creme-crm==2.5'
- If you retrieved the source, you can use the following command at the source's root: 'pip install -e .'
- About DB server :
- If you use MySQL/MariaDB, you must add the 'mysql' flag :
'pip install creme-crm[mysql]==2.5' (or 'pip install -e .[mysql]' with the source).
- For PostGreSQL, you must add the 'pgsql' flag :
'pip install creme-crm[pgsql]==2.5' (or 'pip install -e .[pgsql]' with the source).
- SQLite doesn't require a specific flag (see RECOMMENDATIONS).
- Notice some of these Python packages need system libraries to be installed.
For example, here a list of Debian/Ubuntu packages you'll have to install before:
- python-dev
- mysql_config & libmysqlclient-dev (or libpq-dev if you want to use PostGreSQL)
- redis-server
- libjpeg-dev
- libcairo-dev
### Install
Global remarks:
- You should know how to install/deploy a Django application.
- Upgrade note: if you already have a Creme installation, upgrade the version one by one
(e.g. do not try to upgrade from 2.0 to 2.2, upgrade to 2.1 and then 2.2).
Database configuration:
For a new installation, you have to create a new database & a new DB user
(who is allowed to create/drop tables, indices...).
For an upgrade from the previous major version, back up your existing DB
(of course you should back up regularly, even when you do not upgrade Creme...).
Project creation:
For new installations AND for upgrades from Creme 2.4, create a new project ;
with the virtualenv activated, use the following command which creates a new folder:
```sh
>> creme creme_start_project my_project
```
Settings:
The newly created file "my_project/my_project/settings.py" gives all the information
for a basic installation with the minimal information you must fill.
For an upgrade from the previous version of Creme :
- See the section "UPGRADE NOTE" corresponding to the new version in the file CHANGELOG.txt.
- Do not remove apps in INSTALLED_APPS during the upgrade (because they are installed in your DB) ;
complete your installation & then uninstall apps you do not want anymore (see below).
Filling the DB tables & creating the static asset:
You must be in the parent folder "my_project/" (i.e. not "my_project/my_project/").
Run the following commands (new installations AND upgrades from a previous version):
```sh
>> creme migrate --settings=my_project.settings
>> creme creme_populate --settings=my_project.settings
>> creme generatemedia --settings=my_project.settings
```
Note for MySQL users: you should load the time zone tables.
- On Unix servers, it can be done with:
```sh
>> mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p mysql
```
- For Windows environment, see https://stackoverflow.com/questions/14454304/convert-tz-returns-null
### Launch
To run the development server, you just have to run this command:
```sh
>> creme runserver --settings=my_project.settings
```
You can then go to http://localhost:8000 & log in with root/root.
For a production deployment (Apache, Nginx...), you should read https://docs.djangoproject.com/en/3.2/howto/deployment/
In order to get a completely functional instance, the job manager must be launched
(some features need it: sending emails campaign, CSV import...).
To run it, use this command (in a production environment a watch dog is advised):
```sh
>> creme creme_job_manager --settings=my_project.settings
```
### Uninstall apps
When you have a working installation, & want to remove an (optional) app, use the command 'creme_uninstall' which will
clean the DB. When it's done, you can comment the app in local_settings.py
### Contributing
The repository is using CircleCI and launch some linting tests. To check them locally before any commit or push you can
use the hooks in '.githooks'. There are two ways to configure them:
Simply change git configuration (works with git 2.9+)
```sh
>> git config core.hooksPath .githooks
```
Or create symlink in '.git/hooks/'. Make sure the old one are moved or removed.
```sh
>> ln -s ../../.githooks/pre-commit .git/hooks/pre-commit
>> ln -s ../../.githooks/pre-push .git/hooks/pre-push
```
In order to run the JavaScript linter locally, you can install a NodeJS environment within your virtualenv thanks to the
Python package nodeenv. In your virtualenv (named "mycremeenv"):
```sh
>> pip install nodeenv
>> nodeenv -n 14.20.0 -p # to install nodejs 14.20.0 with "mycremeenv"
>> deactivate
>> workon mycremeenv
>> nodejs --version # to check the installation is OK
>> make node-update # Install nodejs requirements
```
Now you can run "make eslint" manually, and the pre-commit hook will check the new/modified files.
### References
Creme CRM source code is available on the [Creme CRM GitHub Repository](https://github.com/HybirdCorp/creme_crm).
Want to know more about Creme CRM ?
Check out the [Creme CRM Website](https://www.cremecrm.com).
Want to try Creme CRM ?
Visit the [Creme CRM Public Demo Website](https://demos.cremecrm.com/).
Want your own demo instance ?
Pull the latest Creme CRM Demo Docker image on the [Creme CRM DockerHub Repository](https://hub.docker.com/r/cremecrm/cremecrm-demo).
Want to know more about our company ?
Check out the [Hybird Website](https://hybird.org/).
Any other questions ?
Need help ?
Reach us on the [Creme CRM Forums](https://www.cremecrm.com/forum/).
Our (french) [Video tutorials](https://www.youtube.com/channel/UCqt-dsKnW7sNwlCWOODTDWQ).
Raw data
{
"_id": null,
"home_page": "https://www.cremecrm.com",
"name": "creme-crm",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": "CRM",
"author": "hybird.org",
"author_email": "contact@hybird.org",
"download_url": "https://files.pythonhosted.org/packages/10/21/e34776b760189594bc7f9af0ee706a260f237ae02394f7e1fe12896626c6/creme-crm-2.5.7.tar.gz",
"platform": null,
"description": "Creme is a free/open-source Customer Relationship Management software developed by Hybird (www.hybird.org).\n\nIt is designed with an entities/relationships architecture, and is highly configurable, which allows\nadapting Creme to many workflows.\n\n\n\nIt provides apps (i.e. modules) to manage:\n - Contacts & organisations.\n - Documents & folders.\n - Activities (meetings, phone calls, tasks...) with a calendar.\n - Products & services.\n - Invoices, quotes, sales orders & credit notes.\n - Opportunities.\n - Commercial actions.\n - Email campaigns.\n - Reports.\n - Tickets.\n - Alerts, todos & memos.\n - Geolocation.\n - ...\n\nLots of aspects can be configured through a graphical interface :\n - Detailed views for entities are built from blocks ; you can configure which blocks are\n displayed, you can create your own the blocks (chose the fields which are used)...\n - You can configure the columns of the list views (columns can be related to fields, custom-fields,\n relationships...), and filter the lines with powerful rules.\n - You can create your custom-fields, or hide existing fields.\n - You can choose which fields of forms are used, and group them like you want.\n - You can create your own types of relationship, adapted to your business.\n - ...\n\nCreme has powerful tools to filter, search or import data. it provides a credential system with\nsome cool features (teams, allow/forbid entities from a filter on fields/relationships, ...).\n\nIf you have very specific needs, Creme can also be used as a CRM framework to code your own CRM.\n\nCreme is coded in Python, and uses the Django web framework (http://www.djangoproject.com/) and\nthe JQuery javascript library (http://jquery.com/).\n\nYou can find more information on Creme on its official website: http://cremecrm.com/\nYou can ask your questions in our forum: https://www.cremecrm.com/forum/index.php\n(there is an english section)\n\n### Current translations\n\n - English (could probably be improved)\n - French\n\n\n### Recommendations:\n\nIt's recommended to use a database engine which supports transactions :\n - PostGreSQL is probably the best choice for databases with 100,000+ entities.\n - SQLite support is principally done for developers, but it remains a solution\n for small databases (e.g. a use as mono-user app with the server running of your computer).\n\nYou probably should use 'virtualenv' (for an upgrade from Creme 2.4, you should create a new\nvirtual env, in order to keep the old one working).\n\n\n### Dependencies\n\n - Python 3.8+\n - MySQL 8+ (or MariaDB 10.4+) or PostGreSQL 12+ (or SQLite which is included with Python)\n - A web server compatible with Python, like Apache 2.4\n - Redis 3+\n - These Python packages :\n (exact versions of Python packages are indicated in the 'setup.cfg' file)\n - Mandatory :\n - Django\n - redis\n - python-dateutil\n - cryptography\n - bleach\n - Pillow\n - django-formtools\n - xlrd (to import contacts, organisations, activities, tickets... from xls files)\n - xlwt (to export all types of entities -- like contacts or organisations -- as xls files)\n - csscompressor\n - rJSmin\n - Optional :\n - creme.billing :\n If you want PDF export, you can use :\n - xhtml2pdf (default)\n - weasyprint (easy to install on Linux ; harder on Windows)\n - you can also use the binary \"pdflatex\" (Ubuntu package 'texlive-latex-base').\n\nInstallation with 'pip':\n - You should probably use \"virtualenv\".\n - To install Creme itself :\n - You can just install from pyPI: 'pip install creme-crm==2.5'\n - If you retrieved the source, you can use the following command at the source's root: 'pip install -e .'\n - About DB server :\n - If you use MySQL/MariaDB, you must add the 'mysql' flag :\n 'pip install creme-crm[mysql]==2.5' (or 'pip install -e .[mysql]' with the source).\n - For PostGreSQL, you must add the 'pgsql' flag :\n 'pip install creme-crm[pgsql]==2.5' (or 'pip install -e .[pgsql]' with the source).\n - SQLite doesn't require a specific flag (see RECOMMENDATIONS).\n - Notice some of these Python packages need system libraries to be installed.\n For example, here a list of Debian/Ubuntu packages you'll have to install before:\n - python-dev\n - mysql_config & libmysqlclient-dev (or libpq-dev if you want to use PostGreSQL)\n - redis-server\n - libjpeg-dev\n - libcairo-dev\n\n\n### Install\n\nGlobal remarks:\n - You should know how to install/deploy a Django application.\n - Upgrade note: if you already have a Creme installation, upgrade the version one by one\n (e.g. do not try to upgrade from 2.0 to 2.2, upgrade to 2.1 and then 2.2).\n\nDatabase configuration:\nFor a new installation, you have to create a new database & a new DB user\n(who is allowed to create/drop tables, indices...).\nFor an upgrade from the previous major version, back up your existing DB\n(of course you should back up regularly, even when you do not upgrade Creme...).\n\nProject creation:\nFor new installations AND for upgrades from Creme 2.4, create a new project ;\nwith the virtualenv activated, use the following command which creates a new folder:\n```sh\n>> creme creme_start_project my_project\n```\n\nSettings:\nThe newly created file \"my_project/my_project/settings.py\" gives all the information\nfor a basic installation with the minimal information you must fill.\n\nFor an upgrade from the previous version of Creme :\n - See the section \"UPGRADE NOTE\" corresponding to the new version in the file CHANGELOG.txt.\n - Do not remove apps in INSTALLED_APPS during the upgrade (because they are installed in your DB) ;\n complete your installation & then uninstall apps you do not want anymore (see below).\n\n\nFilling the DB tables & creating the static asset:\nYou must be in the parent folder \"my_project/\" (i.e. not \"my_project/my_project/\").\nRun the following commands (new installations AND upgrades from a previous version):\n```sh\n>> creme migrate --settings=my_project.settings\n>> creme creme_populate --settings=my_project.settings\n>> creme generatemedia --settings=my_project.settings\n```\n\nNote for MySQL users: you should load the time zone tables.\n - On Unix servers, it can be done with:\n ```sh\n >> mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p mysql\n ```\n - For Windows environment, see https://stackoverflow.com/questions/14454304/convert-tz-returns-null\n\n\n### Launch\n\nTo run the development server, you just have to run this command:\n```sh\n>> creme runserver --settings=my_project.settings\n```\nYou can then go to http://localhost:8000 & log in with root/root.\n\nFor a production deployment (Apache, Nginx...), you should read https://docs.djangoproject.com/en/3.2/howto/deployment/\n\nIn order to get a completely functional instance, the job manager must be launched\n(some features need it: sending emails campaign, CSV import...).\nTo run it, use this command (in a production environment a watch dog is advised):\n```sh\n>> creme creme_job_manager --settings=my_project.settings\n```\n\n\n### Uninstall apps\n\nWhen you have a working installation, & want to remove an (optional) app, use the command 'creme_uninstall' which will\nclean the DB. When it's done, you can comment the app in local_settings.py\n\n\n### Contributing\n\nThe repository is using CircleCI and launch some linting tests. To check them locally before any commit or push you can\nuse the hooks in '.githooks'. There are two ways to configure them:\n\nSimply change git configuration (works with git 2.9+)\n```sh\n>> git config core.hooksPath .githooks\n```\n\nOr create symlink in '.git/hooks/'. Make sure the old one are moved or removed.\n```sh\n>> ln -s ../../.githooks/pre-commit .git/hooks/pre-commit\n>> ln -s ../../.githooks/pre-push .git/hooks/pre-push\n```\n\nIn order to run the JavaScript linter locally, you can install a NodeJS environment within your virtualenv thanks to the\nPython package nodeenv. In your virtualenv (named \"mycremeenv\"):\n```sh\n>> pip install nodeenv\n>> nodeenv -n 14.20.0 -p # to install nodejs 14.20.0 with \"mycremeenv\"\n>> deactivate\n>> workon mycremeenv\n>> nodejs --version # to check the installation is OK\n>> make node-update # Install nodejs requirements\n```\n\nNow you can run \"make eslint\" manually, and the pre-commit hook will check the new/modified files.\n\n### References\n\nCreme CRM source code is available on the [Creme CRM GitHub Repository](https://github.com/HybirdCorp/creme_crm).\n\nWant to know more about Creme CRM ?\nCheck out the [Creme CRM Website](https://www.cremecrm.com).\n\nWant to try Creme CRM ?\nVisit the [Creme CRM Public Demo Website](https://demos.cremecrm.com/).\n\nWant your own demo instance ?\nPull the latest Creme CRM Demo Docker image on the [Creme CRM DockerHub Repository](https://hub.docker.com/r/cremecrm/cremecrm-demo).\n\nWant to know more about our company ?\nCheck out the [Hybird Website](https://hybird.org/).\n\nAny other questions ?\nNeed help ?\nReach us on the [Creme CRM Forums](https://www.cremecrm.com/forum/).\nOur (french) [Video tutorials](https://www.youtube.com/channel/UCqt-dsKnW7sNwlCWOODTDWQ).\n",
"bugtrack_url": null,
"license": "AGPL-3.0",
"summary": "A CRM software using the django web framework",
"version": "2.5.7",
"project_urls": {
"Homepage": "https://www.cremecrm.com",
"Release notes": "https://raw.githubusercontent.com/HybirdCorp/creme_crm/v2.5/CHANGELOG.txt",
"Source": "https://github.com/HybirdCorp/creme_crm",
"Tracker": "https://github.com/HybirdCorp/creme_crm/issues"
},
"split_keywords": [
"crm"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "031aee2fddf55027af30a423ff7ac464d544e52a914603a34205767f2ab35bb9",
"md5": "725930dfe77c85f828cc8870ef7aab26",
"sha256": "4cf7f52cfa44f937ca4f5eb70b54e81e46428c1d3b89e828173725b1243866f3"
},
"downloads": -1,
"filename": "creme_crm-2.5.7-py3-none-any.whl",
"has_sig": false,
"md5_digest": "725930dfe77c85f828cc8870ef7aab26",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 25727492,
"upload_time": "2024-04-02T08:05:41",
"upload_time_iso_8601": "2024-04-02T08:05:41.649034Z",
"url": "https://files.pythonhosted.org/packages/03/1a/ee2fddf55027af30a423ff7ac464d544e52a914603a34205767f2ab35bb9/creme_crm-2.5.7-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "1021e34776b760189594bc7f9af0ee706a260f237ae02394f7e1fe12896626c6",
"md5": "8ab9aace9e97d452ee79f0011d3686df",
"sha256": "823531e7ec18a29fba7cc50ef4ba0e70da2f5247bfee6eaf2a2350a02b8ec385"
},
"downloads": -1,
"filename": "creme-crm-2.5.7.tar.gz",
"has_sig": false,
"md5_digest": "8ab9aace9e97d452ee79f0011d3686df",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 24039241,
"upload_time": "2024-04-02T08:05:45",
"upload_time_iso_8601": "2024-04-02T08:05:45.384533Z",
"url": "https://files.pythonhosted.org/packages/10/21/e34776b760189594bc7f9af0ee706a260f237ae02394f7e1fe12896626c6/creme-crm-2.5.7.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-04-02 08:05:45",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "HybirdCorp",
"github_project": "creme_crm",
"travis_ci": false,
"coveralls": true,
"github_actions": false,
"circle": true,
"lcname": "creme-crm"
}
JSON
