refactor: replace custom CRM with Monica fork
Some checks failed
Build & Push Monica Image to Gitea Registry / build-and-push (push) Failing after 9s
Some checks failed
Build & Push Monica Image to Gitea Registry / build-and-push (push) Failing after 9s
This commit is contained in:
24
docs/administrators/deployment.md
Normal file
24
docs/administrators/deployment.md
Normal file
@@ -0,0 +1,24 @@
|
||||
This document is aimed at the people deploying Monica on https://monicahq.com, and does not apply to the people installing Monica for their own use.
|
||||
|
||||
## Before deploying a new version
|
||||
|
||||
* Make sure `config/monica.php` contains the number of the new release you are about to create.
|
||||
* Update `CHANGELOG.md` accordingly.
|
||||
* Create a new release on https://version.monicahq.com with the release notes.
|
||||
* Create a new release on https://github.com/monicahq/monica/releases, which will also automatically create a new tag.
|
||||
* Write the release note with the tool hosted on https://monicahq.com/login
|
||||
* Push the code to production.
|
||||
|
||||
## Deployment of the Docker images
|
||||
|
||||
This guide has been posted by [kstrauser](https://github.com/monicahq/monica/issues/676#issuecomment-352047750) - thanks for his help. Here are the steps necessary to deploy Monica on Docker hub:
|
||||
* You need an account on [Docker hub](https://hub.docker.com).
|
||||
* You need to have Docker installed on your machine.
|
||||
* Run the following commands (example for the version 3.4.5):
|
||||
|
||||
```
|
||||
git reset --hard v3.4.5
|
||||
make docker_build docker_tag docker_push
|
||||
```
|
||||
|
||||
The image should be up on the Docker Hub.
|
||||
15
docs/administrators/press.md
Normal file
15
docs/administrators/press.md
Normal file
@@ -0,0 +1,15 @@
|
||||
# Press articles
|
||||
|
||||
Here are all the mentions of Monica we've found on the web somewhere. Feel free to edit this list and submit new ones if you find any.
|
||||
|
||||
* https://blog.desdelinux.net/gestione-relaciones-personales-monica/
|
||||
* https://tideways.io/profiler/blog/profiling-laravel-applications-using-the-open-source-monica-crm-as-example
|
||||
* https://laravel-news.com/monica
|
||||
* https://sivers.org/dbt
|
||||
* https://medevel.com/monica-is-your-own-persona-crm-assistant-solution/
|
||||
* https://www.cloudron.io/store/com.monicahq.cloudronapp.html
|
||||
* https://bestlaravel.com/p/monica
|
||||
* https://betalist.com/startups/monicahq
|
||||
* https://www.bypeople.com/free-personal-crm/
|
||||
* https://steemhunt.com/author/@mindblast/monica-open-source-personal-crm
|
||||
* https://osinum.fr/monica/
|
||||
34
docs/administrators/tips.md
Normal file
34
docs/administrators/tips.md
Normal file
@@ -0,0 +1,34 @@
|
||||
This document lists some tips that developers can use to add new content in Monica and contains the solution to uncommon problems.
|
||||
|
||||
## Add a new changelog entry
|
||||
|
||||
Changelog entries are used to describe what's new in the product. Each time an entry is created, we also need to create an association between users of the instance and the entry that has been created. This association is stored in `changelog_user`.
|
||||
|
||||
To add a new changelog entry, you need to:
|
||||
* create a new entry in the `changelog.json` file in the public folder.
|
||||
* make sure your new entry is at the TOP of the file, not the bottom.
|
||||
|
||||
### When is it relevant to create a changelog entry
|
||||
|
||||
We should not create a changelog entry every single time we make a change to the platform. The rule is to warn users only when we introduce something that they will benefit from. A bug fix is not something they will benefit from and is not worth mentioning. Simple visual changes, unless they drastically change the UI, should not be mentioned. Anything made on the Docker image or a packaging issue should not be mentioned.
|
||||
|
||||
## Failed Jobs queue
|
||||
|
||||
PostgreSQL users who previously failed Monica's update may receive errors similar to these:
|
||||
|
||||
> SQLSTATE[Number]: Duplicate table: 7 ERROR: relation "**failed_jobs**" already exists (SQL: create table "failed_jobs" ("id" bigserial primary key not null, "connection" text not null, "queue" text not null, "payload" text not null, "exception" text not null, "failed_at" timestamp(0) without time zone default CURRENT_TIMESTAMP not null))
|
||||
|
||||
> SQLSTATE[Number]: Duplicate table: 7 ERROR: relation "**failed_jobs**" already exists
|
||||
|
||||
The problem is solved by running the command:
|
||||
|
||||
```
|
||||
php artisan queue:flush
|
||||
```
|
||||
...with the appropriate privileges.
|
||||
|
||||
Immediately after (through a tool like `psql`) access the Monica database and run this command:
|
||||
```
|
||||
DROP TABLE "failed_jobs";
|
||||
```
|
||||
This will ensure that the failed job table has actually been deleted.
|
||||
Reference in New Issue
Block a user