Image Image Image Image Image Image Image Image Image

App Spaces

October 23, 2013 | By | No Comments">No Comments

Today we have deployed our brand new feature called “App Spaces” or simply ‘Spaces’ . You can now have multiple completely isolated search environments under one account. App Spaces can be either environment variations or different applications of your search installation. Moreover you can create spaces which point to different zones like one can work with ‘aws-us’ and other one can at ‘aws-eu’.

searchly-appspaces

You can manage your spaces via “Manage App Spaces” menu at your dashboard. We let you to create 10 “App Spaces” so you have enough room to manage your applications.

PAAS users can not use spaces due to their addon architecture.

Each space is subject to different subscription and resources can not be shared right now. We are open to discuss about resource sharing, let us know your thoughts.

searchly-appspace2

 

You can edit “Name” of a space but region can not be changed. Deleting a space means completely removing all indices, documents and other information related to this space.

While developing spaces we have created new concept of ‘Organisation’ at Searchly. Currently it is hidden however soon, we plan to let our users add additional users to their organisations and we want to add authorisation layer based on roles within an organisation.

All feedback is very welcomed about App Spaces!

Access Keys

July 31, 2013 | By | No Comments">No Comments

SearchBox uses api-keys for authentication to your indices. Api-keys have full control over your account and indices. Many of our users asked us about public api-keys and we are giving you more so-called “access keys”

An access key is a key can be scoped with your indices and aliases with both read-only or full access. This gives you complete tenacity over indices or aliases.

Read-only Access Keys

While creating an access key you can set it as read only and with this key you can “only” execute requests;

  • Search
  • Get
  • MultiGet
  • Get Source

Access Keys With Complete Accees

While creating an access key if you unclick “read only”, created key has now full access to given indices/aliases “except” requests;

  • DeleteIndex
  • CreateIndex
  • All aliases actions

Non-readonly keys can be used for isolating resources without sacrificing index operations, for cases like environments(dev, testqa).

Using Access Keys With Aliases

Indices and aliases handled as same by access keys however this combination has some powerfull outputs.

Aliases can be created with filters. For instance;

If you create an alias to users index named “user_12” with user_id filter, each request made to user_12 will include with that filter.

Now you can create an access-key for this alias and this user will have only access to user_12 alias. With combination of alias filter, that user is completely isolated from other documents, indices and aliases.

Access Keys API

Access keys can be created via dashboard or API

For API details check out documentation

Using ElasticSearch With SearchBox on CloudBees

September 27, 2012 | By | No Comments">No Comments

Introduction

Last week we released the first version of Jest which is the missing ElasticSearch Java HTTP rest client. It covers all core API of ElasticSearch and development of rest of the API is in progress.

During this development we got feedback about using SearchBox with CloudBees.

CloudBees provides an end-to-end application environment that lets developers quickly build, deploy, and scale Java web applications using standard Java frameworks and APIs and libraries, written in any JVM language.

After making Jest ready to battle, we wanted to show you how to make it real.

How ?

Jest has a sample Java application and which is ready to rock but to run with CloudBees it needs small modifications.

Jest uses maven and there is a detailed guide how to use maven with CloudBees here.

Here step by step guide.

  • First clone Jest;
  • Then go to pom.xml and;

Add CloudBees plugin repository after “dependencies”;

Add CloudBees plugin inside “plugins”;

  • You should have 2 things to go further, SearchBox and CloudBees accounts.

Assuming you have got both which are an api-key from SearchBox and an application-id from CloudBees.

  • Find SpringConfiguration.java and change line starts with servers.add(…) with below Java code; (Don’t forget to change “YOUR-API-KEY” with your SearchBox.io api-key.)

All is set, we just need to deploy our application to CloudBees.

  • Change “YOUR-APP-ID” with your CloudBees “application id” and execute it.

You should see an output like something below.

  • Now open your browser and visit you application. You will see “Create Articles”, click it, 2 sample articles will be indexed.
  • Type “Lord” to search box on top right and hit enter, you have a result? Awesome!

As you see, it is very easy to combine powers of SearchBox and CloudBees, I hope you enjoyed it.

Happy coding.