rota3015
e08aeee91b
Updated dbConfig.js file to separate logic from email engine
|
7 月之前 | |
|---|---|---|
| config | 7 月之前 | |
| controllers | 9 月之前 | |
| models | 1 年之前 | |
| routes | 1 年之前 | |
| README.md | 8 月之前 | |
| _site.zip | 9 月之前 | |
| app.js | 1 年之前 | |
| package-lock.json | 1 年之前 | |
| package.json | 1 年之前 | |
| run.sh | 7 月之前 |
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