Página inicial Explorar Ajuda
Registrar Entrar
CommunityRule
/
CommunityRuleBackend
2
0
Fork 0
Arquivos Issues 0 Pull Requests 0 Wiki

Nenhuma descrição

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

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