brucena-choirbook-client

Web Client for the Bruceña Choirbook Project at BC

https://github.com/theportus/brucena-choirbook-client

Science Score: 26.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (11.0%) to scientific vocabulary
Last synced: 9 months ago · JSON representation

Repository

Web Client for the Bruceña Choirbook Project at BC

Basic Info
  • Host: GitHub
  • Owner: thePortus
  • License: mit
  • Language: TypeScript
  • Default Branch: main
  • Size: 114 MB
Statistics
  • Stars: 0
  • Watchers: 1
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Created almost 3 years ago · Last pushed almost 3 years ago
Metadata Files
Readme Contributing License Code of conduct Citation

README.md

brucena-choirbook-client

Sacred Music in Golden Age Salamanca - The Contribution of Susana Muoz and Artus Taberniel


Full Stack (MySQL ExpressJS Angular NodeJS) app for browsing the lost choirbook of Diego de Brucea


Installation

Current installation is on a Docker setup.

Install docker, and docker-compose locally. Then clone this repo and move inside the directory.

sh git clone https://github.com/thePortus/brucena-choirbook-client.git cd brucena-choirbook-client Then, modify the following files with your desired accounts/passwords/ports

``` sh

you must change the server_name and redirect to have the url to which you are deploying

sudo nano nginx/conf/default.conf

client angular settings file MUST contain the IP of the backend

sudo nano src/app/app.settings.ts

the docker config file MUST contain your domain main in the certbot command line

sudo nano docker-compose.yml ```

Run docker compose up -d.

Now, bring the containers down with docker compose down. Then edit the /nginx/conf/default.conf file and uncomment out the lower server block to enable HTTPS traffic. Make sure to replace the server_name with your relevant URLs. Then, bring the containers back up with docker compose up -d.

Finally, set the certbot to autorenew.

sh docker compose run --rm certbot renew

Now uncomment out the second server block code in /nginx/conf/default.conf. Make SURE to put your URL in each relevant spot or the server will not boot correctly.

Finally, restart the server!

sh docker compose up -d

If you have problems and the docker container keeps restarting, the certbot might not have run correctly. To fix this, first, bring down the container with docker compose down. Then, re-comment out the SSH lines in your nginx/nginx.conf file. Now, bring the image back up with docker compose up -d. Then run the command docker compose run --rm certbot certonly --webroot --webroot-path /var/www/certbot/ --email sample@your_domain --agree-tos --no-eff-email -d your_domain -d www.your_domain. Once it is complete, un-comment out the nginx/nginx.conf file and docker compose up -d to get it started.

Develop Locally

If you want to develop locally, you can ignore the docker instructions for the client. First, make sure to set up the server for local development. Once it is started, make sure that your settings in app/app.settings.ts points to the local instance. If you use the server's default values, this should already be the case. Then, run ng serve inside the src directory to run the client locally on port 4200.

Test

To run tests, make sure you are in the src directory. Then run ng test.


Customization

How to Change Site Title/Byline

Edit the src/app.settings.ts file to change any desired display or site information.

How to Change the Fonts

Go to fonts.google.com and select two fonts, one for headers and one for body text. Once you have selected two styles, look under the "Use on the Web" pane in the bottom right. Click the @import option and copy the code BETWEEN the two <style> tags (but don't copy the style tags themselves). Then, go to client/styles.scss and REPLACE line 9 with the new statement (just below where it says 'import google fonts').

Then, on lines 19, 20, and 21 of src/styles.scss, replate the names of the header/body fonts with your new fonts. That almost does it, but there is one last file to change. Edit src/app.settings.ts and change the bodyFont and titleFont properties to match your new fonts.

How to Change the Landing Page

Unfortunately, the landing page does take a little knowledge of Angular to edit. But, you might be able to figure your way around the templates. The files are all located in the src/components/home folder and its subdirectories.

How to Change the Fonts

Go to fonts.google.com and select two fonts, one for headers and one for body text. Once you have selected two styles, look under the "Use on the Web" pane in the bottom right. Click the @import option and copy the code BETWEEN the two <style> tags (but don't copy the style tags themselves). Then, go to src/styles.scss and REPLACE line 9 with the new statement (just below where it says 'import google fonts').

Then, on lines 19, 20, and 21 of src/styles.scss, replate the names of the header/body fonts with your new fonts. That almost does it, but there is one last file to change. Edit src/app.settings.ts and change the bodyFont and titleFont properties to match your new fonts.

How to Change the Landing Page

Unfortunately, the landing page does take a little knowledge of Angular to edit. But, you might be able to figure your way around the templates. The files are all located in the src/components/home folder and its subdirectories.

Owner

  • Name: David J. Thomas
  • Login: thePortus
  • Kind: user
  • Location: Illinois

Digital Scholar, Ancient Historian

GitHub Events

Total
Last Year