User Tools

Site Tools


sis_developer_manual

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
sis_developer_manual [2024/03/11 01:50] – [Deploying the Frontend] ghacheysis_developer_manual [2024/03/11 01:52] (current) – [Packaging the Frontend] ghachey
Line 247: Line 247:
 The deployment can be done in a number of ways. You can use the deployment tools in both the backend and frontend to package the files for the production server. Below explains how. The deployment can be done in a number of ways. You can use the deployment tools in both the backend and frontend to package the files for the production server. Below explains how.
  
-==== Deploying the Backend ====+==== Packaging the Backend ====
  
 Simply use the Visual Studio's publish feature. There is a publish "profile" in there that can be use as example. Two  apps need to be deployed on the backend. Simply use the Visual Studio's publish feature. There is a publish "profile" in there that can be use as example. Two  apps need to be deployed on the backend.
Line 270: Line 270:
 This should package all the frontend files in ''Pacific-SIS/UI/dist/vex/'' This should package all the frontend files in ''Pacific-SIS/UI/dist/vex/''
  
 +==== Deploying to Production Server ====
 +
 +Is a matter of preference. You could simply copy the files produced in the two previous steps and configure the Apache Server to server them. The database will need to also be deployed. One of the maintainers of the system uses Ansible to automate all of these final deployment tasks.
sis_developer_manual.1710121800.txt.gz · Last modified: 2024/03/11 01:50 by ghachey