Browsing projects by Tag(s)

Select a tag to browse associated projects and drill deeper into the tag cloud.

Showing page 1 of 1

Coming soon. Dream big. Insert clichés. Wait long. Release early. Release often. Write sentences. Short sentences. Your web. Your pocket. Go. ConceptThe idea here is to make a web server package which makes projects like XAMPP completely obsolete. A comparison of WAMP software ... [More] packages. We intend to eventually support all packages supported by these systems. And also to run on Windows initially, especially with PortableApps.com support, and later Linux and Mac OS X. The basic plan for usability is: User downloads Manta (base app). Upon first run, they choose easy/advanced package selection. Easy asks them a few questions and suggests packages. Advanced goes to the Package Manager. Package Manager: dependency based. First of all it downloads the packages manifest (probably from SVN, here on Google Code). This contains the list of packages, descriptions, an icon and optional references to screenshots. Also, it contains dependencies, which can be OR-based (e.g. PHP may depend on apache OR lighttpd). When a package is selected for installation, a download script is downloaded (also probably from SVN, here on Google Code) and run. This will download the actual package (which may be from the original site, or it may be a special package of it, hosted here on the Google Code download servers). It may also configure it as needed. Example: I install Apache. It has no dependencies, and works on the Operating System I'm on. Good. Next, I decide I want to install Drupal. I elect to go with Drupal 6. Drupal 6 has as dependencies: PHP 5 or later and MySQL. So Manta goes and installs PHP 5 first, which is dependent upon Apache or lighttpd, but Apache is already there, so it continues and installs PHP 5. Then comes MySQL. During installation of MySQL, it detects the existence of PHP 5, and configures PHP 5 for use with MySQL. These all set up correctly, it installs Drupal 6. Finit. When it comes to updates, Manta can update itself and each package can update itself by re-downloading the install script and running the update functionality. For something like Drupal, it follows meticulously the upgrade path (specifically the updating Drupal 6.x to newer minor version how to) - backing everything up, putting the site into off-line mode, disabling modules and themes, etc. and then putting it back. Then let the user test it and if they're not happy with it, revert to the "restore point" created before the backup. I'll put in here that "restore points" (a.k.a. backups) can be created at any time through the Manta Control Panel. The Manta Control Panel shows what's running, what's not, gives configuration options, help, references to Package Manager, etc. Start-up and shut-down scripts (Python) will also feature, allowing you to customise how your Manta installation works. One other major feature will be support for portability. One major switch will be used which will disable services, ensure path portability, and remove some configuration options which are non-portable in nature. Yes, the portable version may remove some functionality, but be assured that it's functionality that can't be got to work portably. Though if ever you should find a way to make it work, we'd welcome you telling us how :-) Intended Supported PackagesThis is just a brief list of some of the things which Manta will support. Apache HTTP Server, PHP, MySQL and Drupal will be the first ones (in that order) as the first three are the most used ones and Drupal is a good "script" to do, to demonstrate the potential, and to give a challenge in the upgrade script... Minor point updates should be automatically handled by a cron job running from Chris Morgan's server when it's up to that stage, so that you don't need to wait for someone to recognise that Drupal 6.(n+1) has been released and update it for Manta before you can get it. You should be able to get it within an hour of official release. How's that for service? ServersApache HTTP Server lighttpd Apache Tomcat SHTTPD IIS (applicable versions of Windows only, not available in Windows portable version, Linux or Mac OS X) Scripting languagesThe languages which power the scripts, and which generally run in the servers. Python PHP Perl Jaxer Ruby on Rails Glassfish DatabasesMySQL SQLite PostgreSQL Website packagesContent Management Systems, scripts, etc. Django Drupal Wordpress Really, everything supported by systems like Fantastico De Luxe. Except with better support, automatic updates, and proper update support. :-) DevelopmentDevelopment has now started (a bit). Development till it's at a usable state may take a fairly long time, as the main developer Chris Morgan is doing Year 12, and also has various jobs at PortableApps.com which he does. So be patient :-) Development Platform: PHP-GTK [Less]

0
 
  0 reviews  |  0 users  |  751 lines of code  |  0 current contributors  |  Analyzed 9 days ago
 
 
 
 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.