sis_developer_manual
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
sis_developer_manual [2024/03/11 01:45] – [Building and Running the Frontend] ghachey | sis_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 | + | ==== Packaging |
Simply use the Visual Studio' | Simply use the Visual Studio' | ||
Line 260: | Line 260: | ||
This will put the packaged files in specific directories on your development computer based on your publish profile. | This will put the packaged files in specific directories on your development computer based on your publish profile. | ||
- | ==== Deploying | + | ==== Packaging |
Navigate to the '' | Navigate to the '' | ||
Line 270: | Line 270: | ||
This should package all the frontend files in '' | This should package all the frontend files in '' | ||
+ | ==== 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.1710121534.txt.gz · Last modified: 2024/03/11 01:45 by ghachey