github-personal/sysadm
1
0
Fork 0
mirror of https://github.com/outbackdingo/sysadm.git synced 2026-01-27 02:20:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' of github.com:trueos/sysadm

Browse Source
This commit is contained in:
Ken Moore
2017-04-28 09:41:26 -04:00
parent dfb6e1b6a6 cad95cbec8
commit 6392cc362f
5 changed files with 148 additions and 76 deletions
Download Patch File Download Diff File Expand all files Collapse all files

108
README.md
View File

@@ -13,6 +13,23 @@
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
**General Project Information: Table of Contents**
- [General TrueOS Information](#gentrosinfo)
- [TrueOS Project Documentation](#docs)
- [TrueOS Handbook](#trueosdoc)
- [Lumina Handbook](#luminadoc)
- [SysAdm Handbooks](#sysadmdoc)
- [Filing Issues or Feature Requests](#fileissues)
- [Community Channels](#community)
- [Discourse](#discourse)
- [Gitter](#gitter)
- [IRC](#irc)
- [Subreddit](#subreddit)
- [Social Media](#socialmedia)
<!-- END GENERAL INFO TOC -->
# SysAdm
Official repo for TrueOS' sysadm middleware WebSocket & REST server
@@ -105,3 +122,94 @@ have verified the functionality of your new call you should add the output <br /
of the test script (either from copy-n-paste, or from the file /tmp/api-response) <br />
to your commit. (This will allow us to document the new call / class)
# General TrueOS Information <a name="gentrosinfo"></a>
This section describes where you can find more information about TrueOS and its related projects, file new issues on GitHub, and converse with other users or contributors to the project.
## TrueOS Project Documentation <a name="docs"></a>
A number of [Sphinx](http://www.sphinx-doc.org/en/stable/) generated reStructuredText handbooks are available to introduce you to the TrueOS, Lumina, and SysAdm projects. These handbooks are open source, and users are always encouraged to open GitHub issues or fix any errors they find in the documentation.
### TrueOS Handbook <a name="trueosdoc"></a>
TrueOS documentation is hosted on the [TrueOS website](https://www.trueos.org).
The [TrueOS User Guide](https://www.trueos.org/handbook/trueos.html) is a comprehensive guide to install TrueOS, along with post-installation configuration help, recommendations for useful utilities and applications, and a help and support section containing solutions for common issues and links to community and development chat channels for uncommon issues. There is also a chapter describing the experimental TrueOS Pico project and links to the Lumina and SysAdm documentation.
### Lumina Handbook <a name="luminadoc"></a>
The Lumina Desktop Environment has its own [handbook](https://lumina-desktop.org/handbook/), hosted on the [Lumina Website](https://lumina-desktop.org). This handbook contains brief installation instructions. However, due to the highly customizable nature of Lumina, the focus of the handbook lies mainly in documenting all user configurable settings. Each option is typically described in detail, with both text and screenshots. Finally, the suite of unique Qt5 utilities included with Lumina are also documented.
TrueOS users are encouraged to review the Lumina documentation, as the Lumina Desktop Environment is installed by default with TrueOS.
### SysAdm Handbooks <a name="sysadmdoc"></a>
Due to complexity of this project, SysAdm documentation is split into three different guides:
1. **API Reference Guide** (https://api.sysadm.us/getstarted.html)
The Application Programming Interface (API) Reference Guide is a comprehensive library of all API calls and WebSocket requests for SysAdm. In addition to documenting all SysAdm subsystems and classes, the guide provides detailed examples of requests and responses, authentication, and SSL certificate management. This guide is constantly updated, ensuring it provides accurate information at all times.
2. **Client Handbook** (https://sysadm.us/handbook/client/)
The SysAdm Client handbook documents all aspects of the SysAdm client, as well as describing of the PC-BSD system utilities is replaces. Detailed descriptions of utilities such as Appcafe, Life Preserver, and the Boot Environment Manager are contained here, as well as a general guide to using these utilities. TrueOS users are encouraged to reference this guide, as the SysAdm client is included with TrueOS.
3. **Server Handbook** (https://sysadm.us/handbook/server/introduction.html)
The Server handbook is a basic installation guide, walking new users through the process of initializing SysAdm with a bridge and server connection.
## Filing Issues or Feature Requests <a name="fileissues"></a>
Due to the number of repositories under the TrueOS "umbrella", the TrueOS Project consolidates its issue trackers into a few repositories:
* [trueos-core](https://github.com/trueos/trueos-core) : Used for general TrueOS issues, Pico issues, and feature requests.
* [lumina](https://github.com/trueos/lumina) : Issues related to using the Lumina Desktop Environment.
* (Coming Soon) [sysadm](https://github.com/trueos/sysadm) : Issues with using the SysAdm client or server.
* [trueos-docs](https://github.com/trueos/trueos-docs) : Issues related to the TrueOS Handbook.
* [lumina-docs](https://github.com/trueos/lumina-docs) : Issues related to the Lumina Handbook.
* [sysadm-docs](https://github.com/trueos/sysadm-docs) : Issues related to the SysAdm API Guide, Client, and Server Handbooks.
* [trueos-website](https://github.com/trueos/trueos-website) : Issues involving any of the TrueOS Project websites:
- https://www.lumina-desktop.org
- https://www.trueos.org
- https://www.sysadm.us
The TrueOS handbook has detailed instructions to help you report a bug (https://www.trueos.org/handbook/helpsupport.html#report-a-bug). It is recommended to refer to these instructions when creating new GitHub issues. Better bug reports usually result in faster fixes!
To request a feature, open a new issue in one of the related GitHub issue repositories and begin the title with *Feature Request:*.
## Community Channels <a name="community"></a>
The TrueOS community has a wide variety of chat channels and forum options available for users to interact with not only each other, but contributors to the project and the core development team too.
### Discourse <a name="discourse"></a>
TrueOS has a [Discourse channel](https://discourse.trueos.org/) managed concurrently with the TrueOS Subreddit. New users need to sign up with Discourse in order to create posts, but it is possible to view posts without an account.
### Gitter <a name="gitter"></a>
The TrueOS Project uses Gitter to provide real-time chat and collaboration with TrueOS users and developers. Gitter does not require an application to use, but does require a login using either an existing GitHub or Twitter account.
To access the TrueOS Gitter community, point a web browser to https://gitter.im/trueos.
Gitter also maintains a full archive of the chat history. This means lengthy conversations about hardware issues or workarounds are always available for reference. To access the Gitter archive, navigate to the desired TrueOS room’s archive. For example, here is the address of the TrueOS Lobby archive: https://gitter.im/trueos/Lobby/archives.
### IRC <a name="irc"></a>
Like many open source projects, TrueOS has an Internet Relay Chat (IRC) channel so users can chat and get help in real time. To get connected, use this information in your IRC client:
* Server name: irc.freenode.net
* Channel name: #trueos (note the # is required)
### Subreddit <a name="subreddit"></a>
The TrueOS Project also has a [Subreddit](https://www.reddit.com/r/TrueOS/) for users who prefer to use Reddit to ask questions and to search for or post how-tos. A Reddit account is not required in order to read the Subreddit, but it is necessary to create a login account to submit or comment on posts.
## Social Media <a name="socialmedia"></a>
The TrueOS Project also maintains a number of social media accounts you can watch:
* Facebook: https://www.facebook.com/groups/4210443834/
* Linkedin: http://www.linkedin.com/groups?gid=1942544
* TrueOS Blog: https://www.trueos.org/blog/
* Twitter: https://twitter.com/TrueOS_Project/

4
port-files/Makefile
View File

@@ -11,8 +11,8 @@ COMMENT= SysAdm API server
LICENSE= BSD3CLAUSE
WRKSRC_SUBDIR= src
USE_QT5= concurrent core network buildtools qmake gui websockets
USES= pkgconfig tar:xz qmake
USE_QT5= concurrent core network buildtools qmake gui websockets sql
USES= pkgconfig tar:xz qmake ssl
MAKE_ARGS= PREFIX=${STAGEDIR}${PREFIX}
USE_GITHUB= yes

7
port-files/pkg-descr
View File

@@ -1,3 +1,6 @@
Sysadm API server and websocket daemon
SysAdm is a FreeBSD-based service which provides a stable API for
administrating FreeBSD and TrueOS systems. It is composed of a
headless daemon that runs in the background on any system to be
administrated, providing both web socket and REST network services.
WWW: https://github.com/pcbsd/sysadm
WWW: https://sysadm.us

17
src/server/WebBackend.cpp
View File

@@ -647,6 +647,10 @@ RestOutputStruct::ExitCode WebSocket::EvaluateSysadmIocageRequest(const QJsonVal
bool ok = false;
if(keys.contains("action")){
QString act = JsonValueToString(in_args.toObject().value("action"));
QJsonObject retObj;
if(act=="activatepool"){ retObj = sysadm::Iocage::activatePool(in_args.toObject()); }
else if(act=="deactivatepool"){retObj = sysadm::Iocage::deactivatePool(in_args.toObject()); }
/*if(act=="execjail"){
ok = true;
out->insert("execjail", sysadm::Iocage::execJail(in_args.toObject()));
@@ -687,14 +691,6 @@ RestOutputStruct::ExitCode WebSocket::EvaluateSysadmIocageRequest(const QJsonVal
ok = true;
out->insert("capjail", sysadm::Iocage::capJail(in_args.toObject()));
}
else if(act=="deactivatepool"){
ok = true;
out->insert("deactivatepool", sysadm::Iocage::deactivatePool(in_args.toObject()));
}
else if(act=="activatepool"){
ok = true;
out->insert("activatepool", sysadm::Iocage::activatePool(in_args.toObject()));
}
else if(act=="stopjail"){
ok = true;
out->insert("stopjail", sysadm::Iocage::stopJail(in_args.toObject()));
@@ -719,11 +715,12 @@ RestOutputStruct::ExitCode WebSocket::EvaluateSysadmIocageRequest(const QJsonVal
ok = true;
out->insert("listjails", sysadm::Iocage::listReleases());
}*/
ok = !retObj.keys().isEmpty();
if(ok){ out->insert(act,retObj); }
} //end of "action" key usage
//If nothing done - return the proper code
if(!ok){
if(!ok ){
return RestOutputStruct::BADREQUEST;
}
}else{ // if(in_args.isArray()){

88
src/server/library/sysadm-iocage.cpp
View File

@@ -303,6 +303,32 @@ QJsonObject Iocage::cleanJails() {
return retObject;
}
// Stop a jail on the box
QJsonObject Iocage::stopJail(QJsonObject jsin) {
QJsonObject retObject;
if(!jsin.contains("jail_uuid")){ return retObject; }
// Get the key values
QString jail = jsin.value("jail_uuid").toString();
bool success = false;
QString output = General::RunCommand(success, "iocage stop " + jail);
if(success){ retObject.insert("success","jail "+jail+" stopped"); }
else{ retObject.insert("error",output); }
return retObject;
}
// Start a jail on the box
QJsonObject Iocage::startJail(QJsonObject jsin) {
QJsonObject retObject;
if(!jsin.contains("jail_uuid")){ return retObject; }
// Get the key values
QString jail = jsin.value("jail_uuid").toString();
bool success = false;
QString output = General::RunCommand(success, "iocage start " + jail);
if(success){ retObject.insert("success","jail "+jail+" started"); }
else{ retObject.insert("error",output); }
return retObject;
}
// Execute a process in a jail on the box
QJsonObject Iocage::execJail(QJsonObject jsin) {
QJsonObject retObject;
@@ -374,68 +400,6 @@ QJsonObject Iocage::capJail(QJsonObject jsin) {
return retObject;
}
// Stop a jail on the box
QJsonObject Iocage::stopJail(QJsonObject jsin) {
QJsonObject retObject;
QStringList keys = jsin.keys();
if (! keys.contains("jail") ) {
retObject.insert("error", "Missing required keys");
return retObject;
}
// Get the key values
QString jail = jsin.value("jail").toString();
QStringList output = General::RunCommand("iocage stop " + jail).split("\n");
QJsonObject vals;
for ( int i = 0; i < output.size(); i++)
{
if ( output.at(i).isEmpty() )
break;
QString key = output.at(i).simplified().section(":", 0, 0);
QString value = output.at(i).simplified().section(":", 1, 1);
vals.insert(key, value);
}
retObject.insert(jail, vals);
return retObject;
}
// Start a jail on the box
QJsonObject Iocage::startJail(QJsonObject jsin) {
QJsonObject retObject;
QStringList keys = jsin.keys();
if (! keys.contains("jail") ) {
retObject.insert("error", "Missing required keys");
return retObject;
}
// Get the key values
QString jail = jsin.value("jail").toString();
QStringList output = General::RunCommand("iocage start " + jail).split("\n");
QJsonObject vals;
for ( int i = 0; i < output.size(); i++)
{
if ( output.at(i).isEmpty() )
break;
QString key = output.at(i).simplified().section(":", 0, 0);
QString value = output.at(i).simplified().section(":", 1, 1);
vals.insert(key, value);
}
retObject.insert(jail, vals);
return retObject;
}
// Return all the default iocage settings
/*QJsonObject Iocage::getDefaultSettings() {
QJsonObject retObject;