From: "Liam McLoughlin" <hexxeh@hexxeh.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoaster:master commit in: /
Date: Fri, 8 Jul 2011 18:27:09 +0000 (UTC) [thread overview]
Message-ID: <336a7138d7c1cfc8d4db234ed65eb66adb3689d2.hexxeh@gentoo> (raw)
commit: 336a7138d7c1cfc8d4db234ed65eb66adb3689d2
Author: Liam McLoughlin <hexxeh <AT> hexxeh <DOT> net>
AuthorDate: Fri Jul 8 18:26:47 2011 +0000
Commit: Liam McLoughlin <hexxeh <AT> hexxeh <DOT> net>
CommitDate: Fri Jul 8 18:26:47 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gentoaster.git;a=commit;h=336a7138
Added a README with some basic installation/running instructions, removed cachedkernel as default in daemon
---
README | 68 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
create_image.sh | 2 -
daemon.php | 2 +-
3 files changed, 69 insertions(+), 3 deletions(-)
diff --git a/README b/README
new file mode 100644
index 0000000..3019ba6
--- /dev/null
+++ b/README
@@ -0,0 +1,68 @@
+=====================
+= Gentoaster README =
+=====================
+
+Foreword
+=======
+Right now I'm developing this on Ubuntu/Debian, so the following instructions are for those platforms. This will eventually run on Gentoo, of course.
+
+
+Prerequisites
+=============
+
+php5-cli
+php5-dev
+php5-mysql
+gearman-job-server
+gearman-php-ext
+qemu-utils
+extlinux
+sfdisk
+git
+
+There might be more, I'll update this list at some point. Install these as follows: sudo apt-get install php5-cli php5-dev php5-mysql gearman-job-server qemu-utils extlinux sfdisk git
+
+The Gearman PHP extension has to be installed manually, as follows:
+
+wget http://pecl.php.net/get/gearman-0.7.0.tgz
+tar xvf gearman-0.7.0.tgz
+cd gearman-0.7.0
+phpize
+./configure
+make
+sudo make install
+
+Add "extension=gearman.so" to your php.ini (probably /etc/php5/cli/php.ini)
+
+Installation
+============
+
+cd /usr/share
+git clone http://git.overlays.gentoo.org/gitroot/proj/gentoaster.git
+
+
+Running
+=======
+
+There's no init script for the daemon yet, so simply run as follows:
+
+cd /usr/share/gentoaster
+sudo php5 daemon.php
+
+Note the use of sudo, the daemon MUST be ran as root for it to work, otherwise all builds will fail.
+
+Now that the daemon is running, you can try a build, using the sample client:
+
+php5 client.php
+
+This will give you some output similar to the following:
+
+Job sent, handle was H:lucidity:3 - hash 6085655f187a8442f82c43ebf98e5fdb
+
+You can check on the status of that build by running the following:
+
+php5 status.php <handle hash>
+
+Where <handle hash> is the hash returned by client.php (for example 6085655f187a8442f82c43ebf98e5fdb)
+
+If the build is still running, you'll get a progress percentage. If it's finished, the return code and result message will be shown.
diff --git a/create_image.sh b/create_image.sh
index d70cda5..b2d264c 100755
--- a/create_image.sh
+++ b/create_image.sh
@@ -137,7 +137,6 @@ cd rootfs
if [ ! -f ${TOOL_RES_PATH}/stage3.tar.bz2 ];
then
- echo "Downloading Stage 3"
wget ${STAGE3_URL} -O ${TOOL_RES_PATH}/stage3.tar.bz2 &>> ${LOG_FILE} || handle_error "Error downloading Stage3 tarball"
fi
@@ -146,7 +145,6 @@ tar jxf ${TOOL_RES_PATH}/stage3.tar.bz2 &>> ${LOG_FILE} || handle_error "Error e
if [ ! -f ${TOOL_RES_PATH}/portage-latest.tar.bz2 ];
then
- echo "Downloading Portage snapshot"
wget ${PORTAGE_URL} -O ${TOOL_RES_PATH}/portage-latest.tar.bz2 &>> ${LOG_FILE} || handle_error "Error downloading Portage snapshot"
fi
diff --git a/daemon.php b/daemon.php
index a7090f5..8f58076 100644
--- a/daemon.php
+++ b/daemon.php
@@ -45,7 +45,7 @@
if(is_writable($build_path)) {
chdir($build_path);
file_put_contents("config.ini", $configuration_string);
- $tool_args = "--config config.ini --cachedkernel";
+ $tool_args = "--config config.ini";
$process_handle = popen($gentoaster_path."/".$tool_name." ".$tool_args." 2>&1", "r");
$nonstatus_output = "";
next reply other threads:[~2011-07-08 18:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 18:27 Liam McLoughlin [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-23 21:29 [gentoo-commits] proj/gentoaster:master commit in: / Liam McLoughlin
2011-08-19 13:09 Liam McLoughlin
2011-08-15 2:24 Liam McLoughlin
2011-08-15 2:00 Liam McLoughlin
2011-08-15 1:54 Liam McLoughlin
2011-08-14 15:46 Liam McLoughlin
2011-08-12 23:18 Liam McLoughlin
2011-08-12 23:17 Liam McLoughlin
2011-08-12 23:17 Liam McLoughlin
2011-08-11 20:31 [gentoo-commits] proj/gentoaster:webui " Liam McLoughlin
2011-08-12 23:18 ` [gentoo-commits] proj/gentoaster:master " Liam McLoughlin
2011-07-15 20:41 [gentoo-commits] proj/gentoaster:webui " Liam McLoughlin
2011-08-12 23:17 ` [gentoo-commits] proj/gentoaster:master " Liam McLoughlin
2011-07-11 14:00 Liam McLoughlin
2011-07-10 23:53 Liam McLoughlin
2011-07-08 22:41 Liam McLoughlin
2011-07-08 18:47 Liam McLoughlin
2011-07-08 18:35 Liam McLoughlin
2011-07-08 17:27 Liam McLoughlin
2011-07-08 2:45 Liam McLoughlin
2011-06-16 1:01 Liam McLoughlin
2011-06-16 1:01 Liam McLoughlin
2011-06-14 21:28 Liam McLoughlin
2011-06-14 21:03 Liam McLoughlin
2011-06-14 20:44 Liam McLoughlin
2011-06-08 0:06 Liam McLoughlin
2011-06-05 23:32 Liam McLoughlin
2011-06-05 23:32 Liam McLoughlin
2011-06-05 23:32 Liam McLoughlin
2011-06-04 3:47 Liam McLoughlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=336a7138d7c1cfc8d4db234ed65eb66adb3689d2.hexxeh@gentoo \
--to=hexxeh@hexxeh.net \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox