License Portal
Deutsch

LiveConfig 3

Category: LiveConfig
Created: 2022-01-31
Updated: 2024-04-10

At the end of November 2020, we started to fundamentally overhaul LiveConfig. The code base was completely modernized and some critical parts (e.g. the internal server-server communication) were replaced. At the same time, the user interface was also completely redeveloped.

The new architecture now enables functions that were previously not possible, especially in multi-server installations (e.g. web shell or file upload/download). The new REST-API allows the use of all LiveConfig functions by your own applications, and the new web interface runs uniformly and elegantly from smartphone to tablet to PC.

But the best thing is: switching to the new version is possible without any migration effort. The databases from LiveConfig 2.x and 3.x are compatible with each other and you can switch between these versions at any time. Nothing has changed in the creation of the configurations (Lua scripts), so no “side effects” are to be expected.

New functions

  • REST-API - almost all LiveConfig functions are now also conveniently available via a REST-API (“API first” approach). In addition, the REST API can also be used by end customers (authorization for this can be managed separately).
  • New interface - a modern, reactive “single page application” (including Dark Mode)
  • Web Terminal - execute shell commands quickly and easily even without SSH.
  • File Manager - files can be copied and downloaded to the server without an FTP program.
  • Service Control - Display status for all relevant services, real-time update, start/stop/restart/log display via browser.
  • Graphs revised (better display).
  • Backup system with support for Borg, Restic and tar (remote and local).
  • ARM64 support - for servers with an excellent price/performance ratio
  • … and much more (we are gradually expanding the list as we finalize it)

Important changes

  • the SOAP API has been completely removed - the new REST-API is much easier to use and more comprehensive.
  • “Contracts” has been renamed to “Accounts”
  • “My hosting” menu item has been removed (is now also managed under “Accounts”)
  • Several workflows have been simplified (therefore change slightly)

Migration 2.x to 3.x

The migration will proceed exactly as LiveConfig customers are used to: there is no “migration”. Simply update the installed LiveConfig package - done.

The database schema of version 2.x will be compatible with 3.x - in case of doubt, a downgrade is also possible again.

Version 2.x will continue to be maintained in parallel until at least six months after the release of version 3.0, so that there is enough time for the changeover.

What will not change

  • The Lua API will not change for the time being (existing scripts/changes do not have to be adapted), but a major revision of the Lua API is planned in the medium term.
  • Workflow & navigation will not change (except for optimizations)
  • The database schema does not change, you can simply switch from LiveConfig 2.16.x to 3.0.x - and even back.

Schedule / Current development status

We must honestly admit at this point that we have somewhat underestimated the development effort. The new interface in particular brings with it a completely new development workflow which, among other things, made it necessary to redevelop all integration tests. While we were initially confident that we would be able to publish a first release as early as mid/end 2022, it is only now (early 2024) that completion is becoming apparent. In addition, development is taking place parallel to the further development and maintenance of LiveConfig 2.x.

The online demo of LiveConfig 3 already allows you to take a look at the new version. (Username/password: admin/admin)

Milestones

  • 01.02.2024: Start of the closed beta phase
  • April 2024: publicly available beta version
  • as soon as all known issues have been resolved: Release.

Beta phase

From 01.02.2024 at the latest, it will be possible to participate in a closed beta phase. “Closed” means that we only accept beta testers in stages so that we can process the feedback appropriately. We will provide test servers free of charge if required. Further details on the beta test will be available in the forum shortly.

Open issues (status: 10.04.2024)

The following list shows the items currently still open in development (including prioritization):

  • ACME/Let’s Encrypt
    • Completion of order process (backend/plugin) done (01.02.2024)
  • General
    • Integration of backup service (in progress)
    • Quick search done (13.03.2024)
    • Translations
    • AutoDiscover backend handler done (13.02.2024)
    • phpMyAdmin SSO backend handler done (01.02.2024)
    • lcpolicy integration (manage limits, send notifications)
    • AutoDeploy (.json-based initial configuration)
    • CSS customization
  • Administration
    • Delete account (GUI) done (01.02.2024)
    • Delete customer (GUI)
    • Manage reseller prefixes
    • Manage users done (13.02.2024)
    • Dashboard: Onboarding/first configuration status (GUI)
    • Dashboard: Show “recent activity” / log (GUI)
    • Settings: display version/database drivers (GUI) done (20.02.2024)
    • Customers: Show log (API, GUI)
    • Customers: Move / reassign account (API, GUI)
    • Dashboard: Remove preview hint (GUI)
  • Hosting
    • Manage FTP accounts (GUI) done (01.02.2024)
    • Add/edit/delete subdomain (GUI) done (20.02.2024)
    • Manage password protection (GUI) done (19.03.2024)
    • AppInstaller (GUI)
    • Manage cron jobs (GUI) done (08.03.2024)
    • File upload (GUI)
    • Edit file properties (GUI)
    • Manage own DNS entries (GUI)
    • Edit DynDNS settings (GUI)
    • Manage php.ini settings in templates (GUI) done (08.03.2024)
    • manage php.ini settings per account (GUI)
  • IFRAME API
    • Settings -> Own links: Show settings (GUI) done (20.02.2024)
    • Settings -> Own links: Edit settings (GUI) done (20.02.2024)
    • Integrate own links in navigation (GUI, backend) done (08.03.2024)
    • Callback API for checking session data (API)

This list is checked every Tuesday and updated if necessary. Items will only be removed when they are completely finalized.