Skip to main content

Introduction

This recipe installs a Solr server with buildout.

It’s kept as simple as possible and contrary to collective.recipe.solrinstance it does not generate any Solr configuration files. Instead the user can provide a directory containing custom configuration files. A default set of configuration files for usage with Plone is provided.

You can use it by adding a part like this:

[buildout]
parts = solr

[solr]
recipe = ftw.recipe.solr
cores =
    core1

Supported options

The recipe supports the following options:

host

Name or IP address of the Solr server. Defaults to localhost.

port

Server port. Defaults to 8983.

cores

List of cores that should be created.

url

Url for Solr distribution download.

md5sum

MD5 checksum of Solr distribution.

jvm-opts

Can be used to configure JVM options. Defaults to -Xms512m -Xmx512m -Xss256k

conf

Path to a directory containing Solr configuration files.

conf-egg

If provided, the path given in conf is prepended with the path of the given egg.

Metadata

Release files for ftw.recipe.solr 1.3.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ftw.recipe.solr 1.3.2
File Size Uploaded Provenance Actions
ftw.recipe.solr-1.3.2.tar.gz 48.0 kB Without provenance Details for ftw.recipe.solr-1.3.2.tar.gz

Release files / ftw.recipe.solr-1.3.2.tar.gz

Download URL ftw.recipe.solr-1.3.2.tar.gz
Size 48.0 kB
Tags Source
SHA-256 checksum
How to use checksums
c3e20ad17847451dd682b0c725e687987f425258efddcf9c00556662749c816d
BLAKE2b-256 checksum
How to use checksums
50df6bf3b2b37f4676362f2ec6f4abc5f13ab4792a1621df859756a08a08c4dd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.38.0 CPython/3.7.4

Security for ftw.recipe.solr 1.3.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page