Tutorial: an IDE for Alan

  1. Introduction
  2. Application for building applications
  3. Files and folders
  4. Compile and deploy
  5. Your published Application
  6. Next up


In this tutorial you’ll get familiar with the environment for creating Alan applications. For version control and local editing of Alan projects, read this guide.

Application for building applications

For developing Alan applications we typically use an Integrated Development Environment (IDE): an application that provides the developer with a file and folder overview, a text editor that recognises the Alan code, and many other useful tools. In this tutorial we’ll use Visual Studio Code (VS Code) in a Chromium based browser, like Google Chrome or Microsoft Edge:

First window

This screenshot shows the main areas in the layout:

Basic layout

  1. Explorer: overview of files and folders in your project
  2. Text editor: content of open file can be edited here (on startup you’ll see the README.md file with additional info)
  3. Terminal/Output/Problems:
    • Tab ‘Terminal’ for executing instructions (you probably won’t be needing this, but it is active by default)
    • Tab ‘Output’ for output from the compiler (when you want to inspect what happens when you build your project)
    • Tab ‘Problems’ for a nice list of issues from the compiler (this is important when errors occur)

In the top left corner you’ll find these buttons:


They determine what you see in area 1. The top icon is for the Explorer and the only one you’ll need to get started.

At the bottom left side you’ll see these texts:


These are four buttons that execute important tasks:

  1. Alan Fetch downloads and updates the Alan platform tools
  2. Alan Build builds your project
  3. Alan Deploy deploys your project
  4. Alan Show opens an new browser tab with your application

Files and folders

You develop an Alan application by defining application models, defining interfaces, creating migrations, configuring settings, etc. These activities make use of specific files within specific folders. This structure of files and folders is required in order to compile an application. The following files and folders are important while working on the application language tutorial:


The application.alan file in folder models/model contains the model of your application. The migration.alan file in folder migration/from_release (available after your first deployment) describes how your application data needs to be migrated from the current to a next version of your application.

In order to keep focus on the application language, migration files are available for each topic of the tutorial. The location of the relevant files in the folders _docs/tutorials (available in your project) can be found at the end of each topic. By copying and pasting the migration file, your application gets some nice example data for you to experiment with. To make sure you don’t get stuck while working on the Application Language tutorial, the _tutorials folder contains a valid application.alan file for each topic as well.

If, at some point, you seem to miss files or folders in the explorer (area 1) that are referred to in the tutorial, click the refresh button. This button appears when you move your cursor into area 1 (while the online IDE is active):


Files are automatically saved when you:

Save and other options are also available here:


Compile and deploy

Once you’ve written or updated a model and want to see the result, you need to do two things:

  1. Click on the button Alan Build. This will build your model and check for any inconsistencies. Errors occur if your model is not correct. Solve any problems, until you can succesfully build your project.
  2. Click on the button Alan Deploy. This will send your project to the server which will publish (deploy) your application.

NOTE: we recommend that you also run Alan Fetch from time to time (e.g. weekly). This ensures that you have the latest builds of the platform tools at the version specified in your versions.json file. Newer builds should never include breaking changes that break your project build.

Sometimes, you may want to upgrade to a new platform version or system type version. For that, you need to modify the versions.json file. For the latest official platform and system type versions, you can find a versions.json file on the docs page. Make sure to run Alan Fetch to get the right tools after updating your versions.json file.

Your published Application

After deploying your work, you can find the latest published version of your application at the URL provided in the README.md file of your project.

More information about Visual Studio Code can be found here.

Next up

Now you are all set to get started with the application language tutorial, which can be found here. Good luck!