Web-Apps per Mausklick zu installieren war lange der Traum vieler Webseitenbetreiber. Der Traum ist jetzt wahr geworden! Ab sofort können Sie Applikationen aus unserer Bibliothek mit wenigen Mausklicks installieren.
Web-Apps aus diesen Kategorien sind verfügbar:

  • Content Managemet (CMS)
  • Customer Relationship Management (CRM)
  • Help Desk
  • Blog
  • Wiki
  • E-Learning
  • E-Commerce
  • Projekt Management
  • E-Mail
  • Gallerie (Foto)
  • Analyse

Darunter: WordPress, Typo3, MediaWiki, LimeSurvey und viele mehr. Die vollständige Liste finden Sie in unserer Bibliothek.

Eine kurze Einführung finden Sie hier: https://www.tecnostore-group.com/knowledgebase/article/75/wie-richte-ich-web-apps-mit-dem-clearweb-app-installer-ein-/

App-Installer Overview1

When writing tickets for a task to achieve in development or marketing, the results are far better when the ticket is complete and doesnt need a lot of research.

There are tickets for many purposes, support, bugs, requirements, and tasks are just a few of them. This article focuses on requirements and tasks.

For a ticket management to work perfectly it needs to be integrated into the documentation system and revision control. At Tecnostore Group we use the Trac wiki and issue tracking system to achieve this.

The perfect use of such a system eliminates any other flow of information in the development process. Reading a ticket should give the developers and marketing people all the informations needed for the product development.

Defining the requirement

  • What should be implemented: A clear specification of the required functionality / output.
  • Who is the initiator of the idea: For questions and clarifications, also to notify about changes.
  • How should it be implemented: Detailed technical information (e.g. The Ticket “Design splash screen” should contain the desired file format and size)
  • The proper estimated task duration should be between 4 and 16 hours (0.5 to 2 work days)

Analysis / Triage

  • When should it be closed: The target milestone / version
  • How should it be implemented: Detailed technical information (e.g. a Ticket “Design an archive file catalog” could contain the information “Inherit from FileBaseCatalog and write method addToArchive() )
  • A more accurate time estimate.
  • Tickets that are less work than four hours should be merged with related ones. Our Ticket management system knows the resolution “merged” for this.

During Development

  • What was done, a small comment on closing at least.
  • If there was source created it should also be documented by comments.
  • If there were files created that are to be checked into revision control, the log comment has to be linked to the ticket.

What is cloud computing? The basic idea is to have an abstracted model to separate physical IT infrastructure from logical IT infrastructure. Think about the OSI-Layer model and map it to the various infrastructure sets. (e.g. A customer is interested in the availability of a service. He doesnt care about the availability of the exact physical system.) This is called “Infrastructure as a service” short: IaaS

There are other aspects in cloud computing, which provide PaaS (Platform as a Service, e.g. Hosting) or SaaS (Software as a Service, e.g. Salesforce). Since EC2 allows logical
Since EC2 envirements allow a massive scaling of logical infrastructure, often the term “elastic” is used to describe parts of this technology.

EC2 compatible solutions (e.g. Eucalyptus and UEC) provide IaaS Services. The logical it is split into several components:

  • A Cloud Controller: The frontend coordinating everything. It’s accessed by an API, on the client side there are the ec2 tools on the shell or plugins like elasticfox for firefox.
  • A Storage Controller: This unit provides all the storage for the cloud. The storage comes in form of S3 which is also accessible over the web by API tools. It stores files as “Objects” in a “Bucket” objects can be made into “Bundles” by adding a prefix in front of their name. Another form of storage provided is EBS (Elastic Block Storage), which are partition images on the Storage controller, accessible by virtual instances (see below).
  • A Cluster Controller (Eucalyptus term, Amazon refers to clusters as “regions”): This unit controls the physical hardware and network configuration in the cluster.
  • Cloud Nodes: The physical servers running the cloud infrastructure.

The logical infrastructure built in the cloud consists of virtual servers, the so called instances. Instances are stored in form of templates. Every instance launched is started from the template, and looses all changes on termination. So specific configurations and data have to be stored in S3 or EBS. This seems a weird paradigm change at first, but makes perfectly sence, once you look at the migration paths available: Any kind of instance can be upgraded by upgrading and testing the template and then relaunching the instances. This massively reduces migration and administration cost, and makes this tasks just… elastic!

So lautete der Titel des neunten CAOS Report. Erschreckend auf den ersten Blick, hält die Studie aber fest, dass OSS ein Prozess in der Softwareentwicklung sei. Das wiederum ist bekannt, aber was steckt dahinter?

Open Source Business-Modell: Aptana Cloud
Dieser Service bietet SVN, Hosting, Debugging etc für PHP Entwickler. Wer mit der Aptana PHP IDE arbeitet, kann dort seinen Source und seine Applikationen hosten. Der Service kostet US$ 0.04 pro Stunde. Pro Jahr also US$ 350.40. Verglichen mit 3 Jähriger Zend-Lizenz (€ 717.-, ~ CHF 1000.-) + 3 Jahre PHP Hosting mit SSH (SVN auch bald verfügbar), kostet Aptana also gleich viel. (für $ 350.40 gibt es nur 5 GB Space, 10 GB für $ 876.-, 15 GB für $ 1664.40, 25 GB für $ 3241.20 im Jahr).

Dass jeder die IDE Gratis herunterladen kann, macht dabei nichts:

  • Aptana basiert auf Eclipse. OSS dürfte die Entwicklungskosten beträchtlich gesenkt haben.
  • Die Prüfung der Benutzerlizenzen entfällt, das spart Anwälte und Lobby-Kosten.
  • Die freie Weitergabe der Umgebung ist Marketing, das Werbebudget darf tiefer sein.

Aptana ist das beste Beispiel, dass Open Source kein Business-Modell ist, aber viele attraktive Business-Modelle erst ermöglicht.

Als Webworker muss man manchmal viele Formulare ausfüllen, z.B. zum Eintragen von Webseiten auf Linklisten oder Suchmaschinen. Häufig müssen dafür immer die selben Angaben eingetragen werden. Bei Umfangreichen Formularen eine aufwändige Sache.
Das Firefox-Addon “Copy / Paste form” kopiert ganze Formulare auf Klick im Kontextmenü. Anschliessend lassen sich die Werte mit der Kontextmenü-Funktion “Paste Form” wieder ins Formular einfügen. Gerade bei Linklisten eine praktische Sache.

Gemäss diesem Blog-Post eine ganze Menge, hier die Highlights:

Alles Dinge, auf die wir schon lange warten. Schade dass gemäss Roadmap der 5.1 Milestone erst zu 18% erreicht ist. Mit einem Release dürfte man also erst Mitte 2009 rechnen können.