We STRONGLY recommend, that you have a look at our upgrade guide, before upgrading your installation to 1.1.3!
appserver-runtime
which the appserver-dist
package depends onerror.dhtml
templateLdapLoginModule
to allow authentication against an OpenLDAP server@PreAttach
+ @PostDetach
lifecycle callbacks on SSBwebapp
and webapp.name
when parsing datasource XML filesWe STRONGLY recommend, that you have a look at our upgrade guide, before upgrading your installation to 1.1.3!
appserver-runtime
which the appserver-dist
package depends onWe STRONGLY recommend, that you have a look at our upgrade guide, before upgrading your installation to 1.1.2!
appserver-runtime
which the appserver-dist
package depends onAs we've added many new features and enhancements as well as several bugfixes, we STRONGLY recommend, that you have a look at our upgrade guide, before upgrading your installation to 1.1.1! Please do NEVER update your production system WITHOUT test your application locally or on a test system.
appserver-runtime
which the appserver-dist
package depends on@Remove
annotation to allow explicit destruction of SFSBsappserver.xml
and application META-INF/containers.xml
pms-client.properties
file within the `META-INF' directoryepb-client.properties
file within the WEB-INF
directoryMETA-INF/context.xml
web.xml
to allow application specific error pages bound to HTTP response codeappserver-runner
on Windows...During this first Event of his kind at the appserver.io Ecosystem, the Appserver Team members Johann Zelger, Bernhard Wick and Tim Wagner, could gladly welcome nine more attendees of 3 external Companys.
After a 1 hour Introduction to the current State of appserver.io and some Project Historie, the Attendees worked out some interesting Topics to work on at the Hackathon. Therefore, the Attendees split up to Teams to implement the Topics.
Hans Höchtl and Bernhard Wick picked a Feature wish coming from the Team 8select with Andreas Klaiber regarding a current Issue for realisation. On this occasion, it is primarily about the integration of different Application Environments for Development, Staging and Production Context of use. The developer, therefore, will have the possibility to create own specific configuration files for every context of use depending on a surroundings variable during a boot process.
We hope to finish this on time so we can deliver the feature with the next version 1. 1. 1 which gets released in April.
A team all around Michael Döhler dealt with the construction of cluster surroundings in Microsoft Azure based on the most reduced appserver.io-infrastructure and Ansible.
Another goal of the team consisted of replacing the Standard Servlet Engine with a web server module which permits the integration and use of any Frameworks based on the appserver.io Webservers, a lightweight multithreaded web server, written in PHP for PHP.
As a Proof-of-Concept a minimum, functioning Servlet engine which implements a rudimentary Session-Handling on the base of Redis was implemented. The result Bitbucket Repository can be used as a base for own projects.
After installing the current Intellishop Version, Martin Mohr was concentrating on implementing a Console Implementation wich allows managing the Settings on a locale instance of appserver.io. In line with the Hackathon, Martin accomplished to implement a restart command, a command to create or remove a server as well as a command for adjusting Parameters. First Approaches for the Scaffolding are already existing.
After a short settling-in period Ilya Shmygol dealt with the Implementation of a Server-Side-Include module which orientates itself in his functionality strongly by Apache mod_include.
After initial problems, the first barriers could be taken fast and the base functionality of a web server module has been implemented. Ilya will finish the minimum required functionality in the course of the next weeks. The module should be available approximately in one of the next versions of the Community web server and complements the web server around a new and exciting feature.
Already at the...
]]>The following list is a short overview of the great additions you will get with version 1.1.0 "Iron Knight":
You can find a detailed overview of all the fixed bugs and closed issues on our Github Releases page.
Since appserver is a full stack platform, we define the PHP runtime version and the main daemon, which starts all other services, servers and finally the applications. The following updates and features are part of 1.1.0 "Iron Knight" platform.
Version 1.1.x is, as defined in issue #683, now based on PHP 5.6.x and contains many security patches and performance improvements, as well as a whole bunch of new PHP functionality.
The latest version of appserver.io also comes with a completely refactored and improved boostrap process, which is now separated in seven modes of operation, called Runlevels. Below is a list of the different levels:
ID | Name | Description |
---|---|---|
0 | Shutdown | Stop the Application Server |
1 | Administration | Start the Base System |
2 | Daemon | Start the Core Daemons |
3 | Networking | Start the Containers |
4 | Secure | Secure the Application Server |
5 | Full | Initialize and Start the Applications |
6 | Restart | Restart the Application Server |
When appserver.io is started, by invoking service appserver start
on a Linux system's console, Runlevel 5
will be executed. But, prior to this initial server start, all previous Runlevels are actually synchronously executed, whereas
This new boostrap process now uses events, which allows developers, who want to create their own startup functionality, to hook into the runlevel processes to execute their code within the required runlevel. These events can be easily configured through the etc/appserver/conf.d/bootstrap.xml
file. Additionally, there are separate configuration files for the watcher daemon etc/appserver/conf.d/boostrap-watcher.xml
and the setup command etc/appserver/conf.d/bootstrap-command.xml
.
You may be asking yourself, is it possible to switch between the runlevels? Yes, it is! With version 1.1.0, the OS specific init scripts only allowed you to start/stop or restart appserver.io. Now, the Management Console enables developers or admins to login to an instance and allows them to execute various commands, like switching between the runlevels.
This feature had been planned in issue...
]]>We STRONGLY recommend, that you have a look at our upgrade guide, before upgrading your installation to 1.0.6!
appserver-runtime
which the appserver-dist
package depends onWe STRONGLY recommend, that you have a look at our upgrade guide, before upgrading your installation to 1.0.5!
appserver-runtime
which the appserver-dist
package depends onYou might read our upgrade guide, before upgrading to 1.0.4.
appserver-runtime
which the appserver-dist
package depends onThis vulnerability was present in versions prior to 1.0.3 and was exposed by the bundled webserver's HTTP parsing library. The URI as coming from a web client was not normalized correctly which allowed for traversal movement through the file system of the host without the restriction of the configured document root. This allowed for access of otherwise inaccessible files trough specially crafted HTTP requests.
We STRONGLY advise everyone to update to version 1.0.3 or higher.
You might alternatively update the appserver-io/http composer package to version 1.1.1.
]]>