Chapter 4. Resources

Table of Contents

4.1. BASE project site
4.1.1. Download
4.1.2. Ticket system
4.1.3. Roadmap
4.1.4. Documentation
4.2. Core plug-in configurations
4.3. BASE plug-ins site
4.4. Demo server
4.5. Mailing lists
4.6. BASE-hacks

There are several resources available for those who are using BASE or have some other kind of interested in the BASE project. This chapter contains information about those resources and also some short instructions on how to use each one of them.

4.1. BASE project site

The BASE project site is located at Here is a lot of useful information about the project and the program, e.g. documentation/manuals, download-pages, contact information and much more. The most important parts of the page are covered in this section.

4.1.1. Download

The download page is accessed from the download section, on the home page, by following the link to Download Page. From this page you can download BASE releases as packaged tar.gz files or checkout the source code directly from the Subversion repository. See the separate parts on the web page to get more information how to proceed with each one of them.

Packaged BASE releases

Both source-packages and binary-packages are available for each release of the program.

Repository access

With this option the visitor can get the source code directly from Subversion. There are at least three different version that are available to checkout from the repository.

  • The latest production release. This will give you the same source code as one of the packaged releases.

  • The latest non-released bugfix branch. Use this if you are affected by a bug that has been fixed but not yet released.

  • Bleeding edge of the software, which is the latest revision of the program. The code is not guaranteed to work correctly and it is recommended to backup important data in the database before updating. Use this at your own risk, we cannot guarantee that you will be able to upgrade the installation to another version or release.

4.1.2. Ticket system

A ticket is a note about a bug or a new feature that has not yet been implemented. To show the list of outstanding tickets use the View Tickets button on BASE web site. It is a good idea to have a look at this list before reporting a bug or requesting a new feature. Perhaps someone has registered the issue as a ticket already. This list can also be used to see how the BASE development is proceeding and when some particular request is planned to be fixed.

To report bugs, add feature requests, and comment an existing ticket, you needs to be logged in to the trac environment. This is done by clicking on the login-link to the right in the upper corner on the home page. The Feedback-section, also on the home page, contains more information how to proceed.

4.1.3. Roadmap

The roadmap of BASE is accessed from the Roadmap button on the home page. This page contains information about the plans for future development, including the tickets that should be fixed for each milestone. Usually, only the next upcoming release has a date set. The BASE 2.x milestone is used to collected tickets that we think should be fixed but are less important or require too much work. Contributions are welcome.

4.1.4. Documentation

All documentation that are associated with the project can be found in the Documentation-section on the start page.


Useful information for the common user and the administrator, like user documentation, installation instructions and administration guide. These different documents will eventually be replaced with this document when it includes the corresponding texts.


This part contains specification for the separate divisions of the project, such as core specification, web-client specification and more.

Developer information

Information for those who are interested to be involved in the development of BASE.

Future development

Link to a list of ideas for future development that are not covered and monitored in the milestones on the road map page. In other words - ideas that are not planned to be done within nearest 6 to 12 month.

4.2. Core plug-in configurations

In the section called Plug-ins on the home page, is a link to a page that lists the core plug-ins. All plug-ins that are included in the installation of BASE are listed on this page, some together with one or several examples of suitable configuration files. These configuration files can be downloaded and imported with the plug-in configuration importer in BASE.

4.3. BASE plug-ins site

Plug-ins which are not included in the installation of BASE, have their own site, called BASE plug-ins web site which includes a download page for submitted none-core plug-ins. Here is also information how to become a plug-in developer, with commit access to the repository, and how to submit a plug-in to the download page. You will also be able to find example code for plug-ins, extensions, web services, etc.

4.4. Demo server

There is a demo server up running for anyone who wants to explore BASE without having to install it. Follow the link on BASE web site to the demo server or go directly to

Use base2 as login and base2 as password to login to the demo server. The base2 user account has read privileges to all data on the demo server and can view almost every list page. If extended privileges are wanted, please contact the administrator of the demo server (see the bottom of the browser when visiting the demo server).

4.5. Mailing lists

BASE project has three different mailing lists available for subscription. Visit the mailing list page to get more information about each one of the mailing lists. All posted mails are saved in an archive for each list, it can therefore be a good idea to have a look here before posting a new thread.

These are the available mailing lists, more details about each one of them can be found on the mailing list page.

  • basedb-users

  • basedb-devel

  • basedb-announce

4.6. BASE-hacks

There is a trac/subversion server keeping track of changes made to third party projects that are changed to make them work with BASE. Open source project usually have a requirement that changes are made public. On the BASE-hacks web site you will find a list of modified packages and information about the changes performed.