Halite / salt-api: best way to create a custom web interface for salt

112 views
Skip to first unread message

bruno binet

unread,
Jun 13, 2014, 11:09:08 AM6/13/14
to salt-users
Hi list,

For a project we need to create a custom simple web interface with few buttons to easily run a set of custom salt modules.

What is the best way to do it?

I'm aware of both Halite (salt web ui) and salt-api (restful api to salt) projects, but I'm wondering if I should rather customize Halite than use the salt-api in an external application.

By the way, does the Halite web application use the salt-api internally?

As we already use the Halite web app, it may make sense for us to customize Halite instead of doing a completely different application.
Do you know if we can easily extend the Halite web interface, for example by adding a custom renderer that would render an additional web page next to the default interface while still using Halite core engine?

Thanks,
Bruno

Seth House

unread,
Jun 13, 2014, 11:01:45 PM6/13/14
to salt-...@googlegroups.com

On Jun 13, 2014 9:09 AM, "bruno binet" <bruno...@gmail.com> wrote:
> I'm wondering if I should rather customize Halite than use the salt-api in an external application.

I'd suggest looking over the Halite source. If that's something you're interested in customizing it'll give you a nice head start. If not, salt-api was written with web applications in mind so you'll be fine building on it as well.

> By the way, does the Halite web application use the salt-api internally?

It does not use salt-api currently.

> Do you know if we can easily extend the Halite web interface, for example by adding a custom renderer that would render an additional web page next to the default interface while still using Halite core engine?

Halite was written with additional pages/views in mind. (The placeholder tab at the top of the page is an example of this.)

bruno binet

unread,
Jun 16, 2014, 3:17:26 AM6/16/14
to salt-users
On 14 June 2014 05:00, Seth House <se...@eseth.com> wrote:

On Jun 13, 2014 9:09 AM, "bruno binet" <bruno...@gmail.com> wrote:
> I'm wondering if I should rather customize Halite than use the salt-api in an external application.

I'd suggest looking over the Halite source. If that's something you're interested in customizing it'll give you a nice head start. If not, salt-api was written with web applications in mind so you'll be fine building on it as well.

> By the way, does the Halite web application use the salt-api internally?

It does not use salt-api currently.

Do you know why? I guess Halite had to reimplement a kind of own salt-api?

> Do you know if we can easily extend the Halite web interface, for example by adding a custom renderer that would render an additional web page next to the default interface while still using Halite core engine?

Halite was written with additional pages/views in mind. (The placeholder tab at the top of the page is an example of this.)

Cool, that is good to know

--
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Seth House

unread,
Jun 16, 2014, 9:07:35 AM6/16/14
to salt-...@googlegroups.com

On Jun 16, 2014 1:17 AM, "bruno binet" <bruno...@gmail.com> wrote:
> Do you know why? I guess Halite had to reimplement a kind of own salt-api?

This was done to allow Halite to be able to experiment without worrying about maintaining backward compatibility.

Reply all
Reply to author
Forward
0 new messages