12. Deploy Applications
12A. Deploy Apps in LVSCE
- Right-click your program or project in FGL Project Explorer and select Deploy.
- Use Build/Deploy or Rebuild/Deploy for convenience; these actions rewrite output files and object cache.
- To deploy to a custom folder, right-click the program and select Set Custom Deployment Folder. VS Code will offer to choose a path. Provide the path, and click Enter.
Reference: Deploy Apps.
12B. Manual / Command Line Deployment
- Create Object Cache (AOT Compilation): Run qrun --aot to pre-create native code cache at deployment. This reduces execution time.
- Command Example: qrun --aot your_application_name.
- For debug cache: qrun --aot --unl your_application_name.
- Custom Object Cache Path: Set QX_ROOT_OBJECT_CACHE_PATH in settings.json (for LVSCE deployment) and inet.env (for runtime) if you need a custom cache location.
- Copy Files: Manually copy your compiled executables (.exe), intermediate representation files (.4o), external libraries (.4a), and any associated resource files (themes, CSS, database.cfg, .tr2 files) to the AppServer working directory.
- Default AppServer Working Directory (Linux): /opt/Querix/Lycia/progs.
- Resource Files (.tr2): A .tr2 file lists all static resources (images, CSS, JS) that can be used by the application at runtime. If a static file is not included, it won't be accessed.
See next: 13. Run Applications (Debug and Non-Debug Mode)