Differences

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

--- sis_developer_manual [2023/07/19 19:14] – [Database Upgrades] ghachey
+++ sis_developer_manual [2024/03/11 01:52] (current) – [Packaging the Frontend] ghachey
@@ Line 175: / Line 175: @@
                 //var tenant = "opensisv2_ef6";
-                //string connectionString = $"server=localhost;database={tenant};user=opensisadmin;password=!s#4f%grty&1";
+                //string connectionString = $"server=localhost;database={tenant};user=theuser;password=thepassword";
                 //optionsBuilder.UseMySql(connectionString, ServerVersion.AutoDetect(connectionString));
             }
@@ Line 243: / Line 243: @@
+===== Deploying =====
+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.
+==== 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.
+  * opensisAPI
+  * opensis.backgroundjob
+This should look something like this.
+{{ :sis-developer-manual:pacific-sis-deploy-1.png |}}
+This will put the packaged files in specific directories on your development computer based on your publish profile.
+==== Packaging the Frontend ====
+Navigate to the ''Pacific-SIS/UI'' directory and execute the following command.
+<code>
+> ng build
+</code>
+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.