Ana Sayfa Keşfet Yardım
Üye Ol Giriş Yap
CommunityRule
/
CommunityRuleBackend
2
0
Çatalla 0
Dosyalar Sorunlar 0 Değişiklik İstekleri 0 Wiki

Açıklama Yok

Ağaç: ba076dab5c
Dallar Biçim İmleri
CommunityRuleBa...
ZIP TAR.GZ
rota3015 ba076dab5c Changed the logic for email engine and backend also changed the from email address to send mail 6 ay önce
config e08aeee91b Updated dbConfig.js file to separate logic from email engine 6 ay önce
controllers ba076dab5c Changed the logic for email engine and backend also changed the from email address to send mail 6 ay önce
models beb65349b6 first commit 10 ay önce
routes beb65349b6 first commit 10 ay önce
README.md 897277ae13 Update 'README.md' 7 ay önce
_site.zip e9a136494d added zip file 7 ay önce
app.js beb65349b6 first commit 10 ay önce
package-lock.json c97ff664d5 integradted email engine 10 ay önce
package.json c97ff664d5 integradted email engine 10 ay önce
run.sh 055fb04c13 Added run.sh 6 ay önce

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