Differences

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

--- sis_developer_manual [2023/07/19 12:44] – [Database Setup] ghachey
+++ sis_developer_manual [2025/07/10 01:00] (current) – [Frontend Setup] ghachey
@@ Line 139: / Line 139: @@
 ==== Database Upgrades ====
-Database upgrades are done using the .NET EntityFrameworkCore migrations. When a new migration is made available typically in the source code you'll need to apply the migration. This can be done in a number of ways depending on preference and environment (development vs production). One way is to open the Package Manager Console within Visual Studio and run something like the following.
+Database upgrades are done using the .NET EntityFrameworkCore migrations. When a new migration is made available typically in the source code you'll need to apply the migration. In production this will usually happen automatically when accessing the application after the successful upgrade. In development, I usually enable (i.e. uncomment) the commented lines below in the file **opensis.data/Models/CRMContextMySQL.cs** and configure it to run the upgrade on the desired tenant (i.e. database).
+<code csharp>
+using System;
+using System.Collections.Generic;
+using System.Text;
+using Microsoft.EntityFrameworkCore;
+namespace opensis.data.Models
+{
+    public class CRMContextMySQL : CRMContext
+    {
+        private readonly DbContextOptions? contextOptions;
+        public CRMContextMySQL() { }
+        public CRMContextMySQL(DbContextOptions options) : base(options)
+        {
+            this.contextOptions = options;
+        }
+        protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
+        {
+            if (!optionsBuilder.IsConfigured)
+            {
+                //var tenant = "opensisv2_ef6";
+                //string connectionString = $"server=localhost;database={tenant};user=theuser;password=thepassword";
+                //optionsBuilder.UseMySql(connectionString, ServerVersion.AutoDetect(connectionString));
+            }
+        }
+    }
+}
+</code>
+With the above configured the upgrade will run automatically by loading the application. Another way is to open the Package Manager Console within Visual Studio and run something like the following.
 <code>
@@ Line 195: / Line 228: @@
 </code>
+Unfortunately, there is another hidden configuration that needs to be checked in ''Pacific-SIS\UI\src\app\common\default-values.service.ts''
+<code javascript>
+setDefaultTenant() {
+    const url = window.location.href;
+    let tenant = '';
+    if (url.includes('localhost')) {
+      // sessionStorage.setItem('tenant', JSON.stringify('opensisv2_ef6'));
+      //tenant = 'fedsis';
+      sessionStorage.setItem('tenant', JSON.stringify('fedsis'));
+      tenant = 'fedsis';
+    } else {
+      let startIndex = url.indexOf('//');
+      let endIndex = url.indexOf('.');
+      let tenantName = url.substr(startIndex + 2, endIndex - (startIndex + 2));
+      sessionStorage.setItem('tenant', JSON.stringify(tenantName));
+      tenant = tenantName;
+    }
+    this.commonModel._tenantName = tenant;
+  }
+</code>
 ==== Building and Running the Frontend ====
@@ Line 208: / Line 264: @@
+===== 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.