The OSF IDE (Integrated Development Environment) is a web based tool to develop and manage your application with the OSF. This tool is included along with the OSF download on its Download page.
The OSF IDE can be accessed at the URL:
Application Settings refer to setup information that are used while installing the OSF, thus setting up the application with the OSF. This includes application name, description, author name, email address of admin user, URL of application and database settings. Database settings include DSN, Database Name, DB user and Password, and Table Prefix (the string that will be preppended to each table of the application including the OSF Database Tables).
You can edit the application settings on the OSF IDE. But you need to be careful about Application Base URL as it may make the application disfunctional. However, you can manage your Lifestream log (enabling and disabling) here apart from other aspects of application. There is no facility to edit database settings for an application as there is a separate utility (currently under development) to help you migrate your application to different database and different location.
The OSF has an inbuilt capability to track the access to the application created through it. This is enabled by default during installation of the OSF. You can see the access log of the application in the section meant for Lifestream on the OSF IDE.
Each day log is stored in separate text files, and creates a new row on the Lifestream page on the OSF IDE. The log files are stored in the directory
/log, and rows of log file looks like the following (two lines of a successfully executed event have been presented for illustration):
25 March 2010, 7:10 am - Application accessed by user admin through URL /appl/index.php?ID=6 from IP
127.0.0.1. 25 March 2010, 7:10 am - Application executed in 0.1765148639679 sec.
The first line above describes the access by user (if it is public access, no user information will be present), and the second line describes the successful execution of the event. In case of failure in execution of event, the second line will be absent in the log. As the log stores critical information like user, URL, IP from which access is done and time for execution of event, it is very useful to study the performance of application.
The IDE has utility to delete log of any particular day, and also to remove the entire history of access log.
You may like to disable the Lifestream log (this can be done by editing the Application Settings) as it produces daily log files and thus consumes disk space. But it is advisable to keep it enabled, and to remove the history periodically. The removal of history is extremely critical on high-traffic sites or applications.
Updated on Aug 20, 2016
The techReview is an online magazine by Batoi and publishes articles on current trends in technologies across different industry verticals and areas of research. The objective of the online magazine to provide an insight into cutting-edge technologies in their evolution from labs to market.