SaaS CMS has officially launched! Learn more now.

Dan Matthews
May 24, 2016
  2794
(4 votes)

Vulcan goes Nuggety and gets a UI

Today marks a significant milestone in the journey of Vulcan, the lightweight Elasticsearch client for Episerver. It’s going onto the Episerver Nuget Feed which will make it more readily available to more people, and it now has a UI. It’s still very lightweight, but it now supports index-time synonyms. Unlike Episerver Find, which supports more dynamic synonyms, Vulcan processes synonyms on objects at index time and as Vulcan manages your objects for you that means there has to be a way to register synonyms with it. For now, that’s all the UI does although maybe it will be extended later.  Note that once you’ve added/removed synonyms, you’ll need to a re-index your content with the scheduled job. And yes… I’m useless at user interfaces, and so it’s basic. Very basic. But it does the job! Enter the synonyms comma-delimited. I also added a small count of types just so that you can see what each of your language clients contains.

image

So how do you install Vulcan from the Nuget feed? In Visual Studio, browse the Episerver Nuget package (or search it for ‘Vulcan’) and you’ll see three Nuget packages: TcbInternetSolutions.Vulcan.Core, TcbInternetSolutions.Vulcan.UI and TcbInternetSolutions.Vulcan.Commerce.

image

The Core package contains the core of Vulcan and the content indexer. The UI package contains a shell module that adds the UI for managing synonyms. The Commerce package is only required for an Episerver Commerce site – it simply ensures that Vulcan will index the product catalogue as well as the CMS content. The dependencies are set between them so if you install the UI or Commerce package it will pull the Core one down automatically too. Once you’ve installed Vulcan, look in the web.config for the text ‘SET THIS’ and set your Elasticsearch Url and Index name. Optionally, depending on where you are connecting to, you may need to add the VulcanUsername and VulcanPassword app settings keys as well (they aren’t automatically added because you might well be using Elasticsearch locally, for example). Then run your Vulcan Index Content scheduled job (if you go to the UI before you do this, it won’t find any clients.) Now you should be good to search and use the UI. Enjoy!

DISCLAIMER: This project is in no way connected with or endorsed by Episerver. It is being created under the auspices of a South African company and is entirely separate to what I do as an Episerver employee.

May 24, 2016

Comments

Please login to comment.
Latest blogs
Optimizely release SaaS CMS

Discover the future of content management with Optimizely SaaS CMS. Enjoy seamless updates, reduced costs, and enhanced flexibility for developers...

Andy Blyth | Jul 17, 2024 | Syndicated blog

A day in the life of an Optimizely Developer - London Meetup 2024

Hello and welcome to another instalment of A Day In The Life Of An Optimizely Developer. Last night (11th July 2024) I was excited to have attended...

Graham Carr | Jul 16, 2024

Creating Custom Actors for Optimizely Forms

Optimizely Forms is a powerful tool for creating web forms for various purposes such as registrations, job applications, surveys, etc. By default,...

Nahid | Jul 16, 2024

Optimizely SaaS CMS Concepts and Terminologies

Whether you're a new user of Optimizely CMS or a veteran who have been through the evolution of it, the SaaS CMS is bringing some new concepts and...

Patrick Lam | Jul 15, 2024

How to have a link plugin with extra link id attribute in TinyMce

Introduce Optimizely CMS Editing is using TinyMce for editing rich-text content. We need to use this control a lot in CMS site for kind of WYSWYG...

Binh Nguyen Thi | Jul 13, 2024

Create your first demo site with Optimizely SaaS/Visual Builder

Hello everyone, We are very excited about the launch of our SaaS CMS and the new Visual Builder that comes with it. Since it is the first time you'...

Patrick Lam | Jul 11, 2024