Meilisearch | Meilisearch Cloud | Documentation | Discord | Roadmap | Website | FAQ
☁ Meilisearch tools for the Cloud ☁
Meilisearch Cloud Providers is a set of tools and scripts allowing to build Meilisearch images for multiple platforms made with Packer.
Meilisearch is an open-source search engine. Discover what Meilisearch is!
- 🎁 Content of this repository
- ⚡ Supercharge your Meilisearch experience
- 📖 Providers available
- 📖 Documentation
- 🔧 Prerequisites
- 🔑 Set your credentials
- 🚀 Getting Started
Say goodbye to server deployment and manual updates with Meilisearch Cloud. Get started with a 14-day free trial! No credit card required.
These Packer build configurations are used primarily by the Meilisearch integration team, aiming to provide our users simple ways to deploy and configure Meilisearch in the cloud by creating ready-made images of Meilisearch. As our heart resides in the open-source community, we maintain several of these tools as open-source repositories.
| Cloud Provider |
|---|
| AWS |
| DigitalOcean |
| GCP |
See our Documentation or our API References.
You need the following to run the template:
- The Packer CLI v1.8.6+ installed locally
- Obtain your AWS access keys
- Obtain your DigitalOcean API Token
- Obtain your GCP credentials
- Aws
export AWS_ACCESS_KEY_ID="YOUR_ACCESS_KEY"
export AWS_SECRET_ACCESS_KEY="YOUR_SECRET_KEY"- DigitalOcean
export DIGITALOCEAN_TOKEN="XxXxxxxXXxxXXxxXXxxxXXXxXxXxXX"- GCP
export GOOGLE_APPLICATION_CREDENTIALS="path_to_your_creadential_file.json"Download and install packer plugins
packer init .⚠ Please note that this command will create all new Meilisearch images on all platforms of the specified version.
packer build meilisearch.pkr.hcl⚠ Please note that this command will create new Meilisearch image on the dedicated platforms of the specified version.
packer build -only 'amazon-ebs.*' .packer build -only 'digitalocean.*' .packer build -only 'googlecompute.*' .If you want to learn how to deploy a Meilisearch instance on DigitalOcean visit the dedicated page of our documentation: