| Summary | Create a Horde .ami image |
| Queue | Horde Base |
| Queue Version | Git master |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | Chuck Hagenbuch <chuck (at) horde (dot) org> |
| Created | 07/05/2009 (1421 days ago) |
| Due | |
| Updated | 01/30/2013 (116 days ago) |
| Assigned | |
| Resolved | 01/30/2013 (116 days ago) |
| Attachments | |
| Milestone | |
| Patch | No |
groupware release?"
Yes, it's possible. I run a script which re-packages horde pear
packages to rpm as they pop up in the channel. I can add a build
target "image" to obs which builds essentially the same VM as the
SUSE Studio. The pro is the automation. No need to manually trigger
the build. The con is there is no nice GUI - I'd have to provide and
update a download link on my own. But since the obs has an API, it may
be scriptable.
State ⇒ Resolved
State ⇒ Feedback
Version ⇒ Git master
the Groupware, now that is has been released. It might be easiest to
run the install script with expect.
Of course the missing IMAP server has to be installed too at some
point. Big bonus points for SQL integration so that new users can be
added through the Horde user management.
Is there any way to (semi-)automate this build when we do a new
groupware release?
no additional setup.
appliance for EC2, xen, vmdk & other formats
See http://susegallery.com/a/BZ4vzQ/kde4-horde4-demo-setup
State ⇒ Accepted
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Base
Summary ⇒ Create a Horde .ami image
Type ⇒ Enhancement
Priority ⇒ 1. Low
no additional setup.