-
Notifications
You must be signed in to change notification settings - Fork 2
Deployment and Configuration
Information for deploying and configuring the CAE itself can be found here. (TBC)
Building the service is just building a las2peer service. The las2peer template project and its wiki contain detailed information, but basically you should be able to clone the repository and execute a build using ant.
To set up your own CAE instance some work is required. This should give you an overview of the dependencies and preparatory steps. You can also use the Kubernetes configurations in main CAE repo. If you want to set it up to your local environment, you can install minikube and use Kubernetes configurations in this local Kubernetes cluster.
Build the model persistence service and code generation service from source as described above. You can also download jar files from the GitHub releases, but building the current master branch is recommended.
The model persistence service needs a database to store model data. JDBC is used for database connectivity and the .properties file contains the corresponding settings. By default it contains settings for a mysql database, just fill in the schema, user and password you want to use. To initialize your database for use with the model persistence service import the ModelPersistenceService_Database.sql file frome the database folder. By default the database name "commedit" is assumed.
The CAE uses GitHub organizations as a central place for its generated code's repositories. Create a GitHub organization and enter its name in the code generation service's .properties file. Then fork the CAE-Template repository to your organization. The default name is CAE-Templates, if you want to use another one, e.g. your own templates, change the name in the .properties file.
Docker container of CAE Frontend application need to be started in order to access CAE Frontend. Docker image can be found in here. Necessary instructions to start Docker container can be found in respective Github repo. When container started to run, application will have all the pre-configured modeling spaces such as microservice, frontend and application modelling spaces.