PAS Code Preview
Please note that PAS Code and its documentation are currently available only in a preview version. We are working on improving the product every day, so the content and user interfaces may still change. We are eager to receive your feedback on the product and the documentation. Send your message to support@scheer-pas.com.
This guide will help you become familiar with the key features you’ll use in every PAS Code project. It walks you through the steps of creating, developing, and deploying a project from initial setup to your first push.
Prerequisites
To get started with PAS Code, your development environment must meet the following requirements:
-
Node.js: LTS Version 24.7 or later (refer to Node.js homepage for downloads).
-
Code Editor: We recommend Visual Studio Code (refer to Visual Studio Code homepage for downloads).
-
Operating Systems: MacOS, Windows and Linux.
-
Terminal: Required for running PAS CLI commands.
Expert Advice
If you are an experienced developer and want to work with different versions of Node.js, we recommend using nvm. For the installation of nvm refer to github > nvm-sh/nvm.
If you use nvm, you can install the latest version of Node.js with the following command:
nvm install --lts
The PAS Code Development Workflow
Development with PAS Code can be completed in just a few simple steps. Generating your project is the start, next implement your services, agents, and apps with the shared Scheer PAS libraries while an AI coding assistant follows the platform conventions for you. Finally deploy your project, and let the platform run, route, configure, and monitor it.
The following table shows the most important commands of the PAS Code workflow:
|
Step |
Command |
Description |
|
1 |
|
Connect the PAS CLI to a PAS platform. |
|
2 |
|
Create a new PAS Code project. |
|
3 |
|
Create application, service, or (agent). |
|
4 |
|
Local development (fastest option). |
|
5 |
|
Deploy to a PAS development environment (PAS platform’s Git repository). |
Step 1: Connecting to the PAS Platform
With PAS Code, you can develop locally (refer to Getting Started With PAS Code for details on local setup), but you can also connect the PAS CLI to your PAS platform.
The following command authenticates you and sets up your access to the git hosting platform (SSH keys and user provisioning):
pas platform login <platform-url>
The command opens the browser for authentication, stores the platform connection, and attempts to register an SSH key for Git access. Verify the connection with:
pas platform list
Step 2: Creating a New PAS Code Project
You are connected to your PAS platform, now you need to create a project. You have two options:
-
You can create a PAS Code project containing an example. The example project is created with all necessary folders and a demo application. You can use the example project:
-
to make yourself familiar with the contents of a PAS Code project.
-
if you don't want to start from scratch, but would like to adapt a sample content to your needs.
-
-
You can create a PAS Code project without sample content and create everything manually.
(1) Creating an Example PAS Code Project
To create a new PAS Code project, run the following command (where my-project is the name of your project, so exchange this with a name of your choice):
pas new my-project
If you want to track all the details of the creation process, use the following:
pas new my-project --verbose
After scaffolding, the CLI asks: ? Create a project on the active PAS platform? (Y/n)
-
Yes: The CLI automatically creates a Gitea repository and pushes the code immediately.
-
No: The project is created entirely locally. To push your code, you can use
pas platfrom git create-repositorylater.
(2) Creating an Empty PAS Code Project
To create a new, empty PAS Code example project without the example app, run the following command:
pas new my-project --skip-example
If you want to track all the details of the creation process, use the following:
pas new my-project --skip-example --verbose
After scaffolding, the CLI asks: ? Create a project on the active PAS platform? (Y/n)
-
Yes: The CLI automatically creates a Gitea repository and pushes the code immediately.
-
No: The project is created entirely locally. To push your code, you can use
pas platfrom git create-repositorylater.
Step 3: Developing Locally
Inside your project, you can now generate a frontend application (Angular) or a backend service (Nest.js). Projects are placed in packages/<name>/. The framework enforces architectural standards (Borders) and includes PAS-specific libraries by default.
Use PAS generators to add application components.
Generating an Angular Application
To generate a frontend application, use the following command:
pas generate app <app-name>
The frontend is available at http://localhost:4200.
Generating a Nest.js Service
To generate a backend service, use the following command:
pas generate service <sevice-name>
The backend is available at http://localhost:8080.
Start your application locally for fast development with instant hot-reload:
pas start
-
Speed: Millisecond hot-reload.
-
Environment: Runs natively on your machine (no containers).
Develop and test the components locally before publishing.
Step 4: Pushing a Project to the Platform
When your code is ready, commit the changes using the PAS conventional commit format, then push the branch to the platform's Git repository:
git add .
git commit -m "feat: add application functionality"
git push
The push starts the platform pipeline. The pipeline builds the project components, creates a version, publishes the images and configuration, and registers the version with the platform.
Push/merge on main triggers the build and deploy pipeline. Publishing a tag also triggers the pipeline. In addition to main, additional branches can be configured; however, only an administrator can currently do so.
Step 5: Accessing Your Application
Open the Control Hub and find the published project in the Projects view. Select a published version, deploy it to an environment, and open the application's generated URL.
Refer to The Control Hub for more information.
Each later change follows the same cycle: develop locally, verify the change, commit, push, and deploy the new version to the Control Hub.
Related Content
Related Pages: