Vesta Control Panel - Forum

Is there a recommended approach to extending the admin API in Vesta?

For example, if I have another command line tool that I would like to make available through the Vesta admin api.

Any examples that I could perhaps take a look at or that would make a good starting point?

Thanks

For now you can put additional scripts in /usr/local/vesta/bin/ and they will become available via API. Unfortunately, such method isn't sustainable across updates.

I will think about how we can cover this in feature releases.

skid wrote:For now you can put additional scripts in /usr/local/vesta/bin/ and they will become available via API. Unfortunately, such method isn't sustainable across updates.

I will think about how we can cover this in feature releases.

Thanks skid. If I do add scripts now, do you think the updates will wipe them or just make them inoperable?

That's a good question. It all depends on system package manager and it seems like rpm doesn't wipe bin directory. Not sure about dpkg. I will check it later today.

Thanks. At the moment I'm not sure whether to put my additions somewhere else with their own API or try and integrate them with the Vesta API.

I have a good news, apt-get upgrade didn't wiped directory. So you are safe to go.

Fantastic. The approach I have taken so far has been to create additional v-xxxx-xxx-xxx commands. Works perfectly from the command line but I've yet to test it through the API.

Do you know if 'apt-get upgrade' does much to the 'skel' in the vesta templates?

Anything in /usr/local/vesta/data is beyond the apt or yum knowledge. Feel free to modify and change any file there.

:-) this just gets better and better.

API documentation and examples:
http://vestacp.com/docs/API.pdf

CLI commands list and descriptions:
http://vestacp.com/docs/CLI.txt

-> viewtopic.php?f=18&t=12610