Accueil Explorer Aide
S'inscrire Connexion
CommunityRule
/
CommunityRuleBackend
2
0
Fork 0
Fichiers Tickets 0 Pull Requests 0 Wiki

Aucune description

Aborescence: e08aeee91b
Branches Tags
CommunityRuleBa...
ZIP TAR.GZ
rota3015 e08aeee91b Updated dbConfig.js file to separate logic from email engine il y a 7 mois
config e08aeee91b Updated dbConfig.js file to separate logic from email engine il y a 7 mois
controllers 56f4c8f07c Changed the email message il y a 9 mois
models beb65349b6 first commit il y a 1 an
routes beb65349b6 first commit il y a 1 an
README.md 897277ae13 Update 'README.md' il y a 8 mois
_site.zip e9a136494d added zip file il y a 9 mois
app.js beb65349b6 first commit il y a 1 an
package-lock.json c97ff664d5 integradted email engine il y a 1 an
package.json c97ff664d5 integradted email engine il y a 1 an
run.sh 055fb04c13 Added run.sh il y a 7 mois

README.md

Backend

  • Our code is present at /app/data/public/communityRuleBackend.
  • Our backend is being running on port 3000.
  • Internally, there is one run.sh which is responsible to run any script on start of the server. We are running another run.sh which is in our public/communityRuleBackend/run.sh which is kind of for loop which will keep on running and check every 30 mins if our backend is working or not if it is not working it will start the backend.
  • Our database is also present in the same cloudrun environment
  • We are using email engine provided by cloudrun
  • Details regarding database and email is present in code dbConfig and emailConfig