• If you are like me and a late-comer to the Docker party the following pages should help you find your way around in the Docker world.

• Docker is an open-source platform that simplifies building, shipping, and running applications by using containerization.
• It packages an application with everything it needs to run—code, runtime, libraries, and system tools—into a single, portable unit called a container.

• I would recommend if the following terms are all new to you that you read this section every day for the newt couple of days so some of the buzzwords stick

There are two primary items that can trip you up.

1. An Image
2. A Container

• The image comes first and are used to produce one or more containers.
• Image = recipe / blueprint
• Container = actual meal / house built from that blueprint

• Read-only template
• Contains the OS, code, libraries, env variables — everything needed to run
• You build it or pull it: (e.g. docker pull nginx)
• It sits there, does nothing until you run it
• You can make 100 copies from one image
• Like a class in programming

• RADIUSdesk is designed in such a way that there is a hard separation between the GUI and the web application providing data to the GUI.
• We use Ext JS for the GUI.
• Ext JS Classic is used with laptop and desktop browsers.
• Ext JS Modern is used with mobile devices.
• All the actions that the GUI do are API calls to a CakePHP web application.
• This means that it is easy to determine the URL and data required for an action.
• This also means that the API calls can be done by any other system thus making third party integration a snap.
• Each API call has to include a token which is associated with the user that logged in on the RADIUSdesk GUI.
• Most of the API calls will also include a cloud_id to indicate on which cloud the action is to be applied.

• Many larger ISPs that makes use of RADIUSdesk prefer it above the commercial one size fits all solutions that already includes CRM and billing components.
• RADIUSdesk allows for easy integration with existing CRM systems and middle-ware.
• See the diagram below which illustrates the possibilities.

• Common actions include:
  • Adding Profiles.
  • Adding Realms.
  • Adding Permanent Users.
  • Disabling and Enabling Permanent Users.
  • Changing Permanent User Profiles.
  • Terminating a Permanent User's session.
  • Deleting a Permanent User.
• We will cover how to do these actions using the API in dedicated Wiki pages.