nextcloud / nextcloud/fulltextsearch
Wiki systemd suggestion
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Hello there,
I had some issues with the suggested nextcloud-fulltext-elasticsearch-worker.service as it stopped and did not came back due to Index is already running.
I added a ExecStarPre parameter to stop any indexing and also reduced the retry time to three seconds:
[Unit]
Description=Elasticsearch Worker for Nextcloud Fulltext Search
After=network.target
[Service]
User=www-data
Group=www-data
WorkingDirectory=/var/www/cloud
ExecStartPre=/usr/bin/php /var/www/cloud/occ fulltextsearch:stop
ExecStart=/usr/bin/php /var/www/cloud/occ fulltextsearch:live -q
ExecStop=/usr/bin/php /var/www/cloud/occ fulltextsearch:stop
Nice=19
Restart=always
RestartSec=3
[Install]
WantedBy=multi-user.target
Unfortunately I do not know how to add a PR to the wiki.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the wiki page containing the suggested nextcloud-fulltext-elasticsearch-worker.service configuration. Compare the example with the supplied unit and update the documented service settings, then verify the wiki formatting and that the example reflects the intended restart behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, php
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100