Issue-690: Separate CI/CD workflows

[rishabmamgai]

Contributor checklist

• [] This pull request is on a separate branch and not the main branch
• [] I have run the tests for the backend and frontend depending on what's needed for my changes as described in the testing section of the contributing guide

---

Description

Creates separate workflows for CI/CD.

To test docker image locally -

1. Create docker network. docker network create my_network
2. Run postgres image. docker run -e POSTGRES_DB=activist -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -d --network=my_network postgres
3. Update DATABASE_HOST in .env.dev, then build and run. docker build --build-arg env=prod -t activist_backend . docker run --env-file ../.env.dev --network my_network activist_backend:latest

Related issue

• #690

[github-actions[bot]]

Thank you for the pull request! ❤️

The activist team will do our best to address your contribution as soon as we can. If you're not already a member of our public Matrix community, please consider joining! We'd suggest that you use the Element client as well as Element X for a mobile app, and definitely join the General and Development rooms once you're in. Also consider attending our bi-weekly Saturday developer syncs! It'd be great to meet you 😊

[netlify[bot]]

✅ Deploy Preview for activist-org canceled.

Name	Link
🔨 Latest commit	4e3ebddd158a79797d4d6926a4e084d9233386b6
🔍 Latest deploy log	https://app.netlify.com/projects/activist-org/deploys/68a1eb78bf03e700086ba110

[github-actions[bot]]

Maintainer Checklist

The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

• [ ] The TypeScript, pytest and formatting workflows within the PR checks do not indicate new errors in the files changed

• [ ] The Playwright end to end and Zap penetration tests have been ran and are passing (if necessary)

• [ ] The changelog has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[andrewtavis]

Thanks for the PR, @rishabmamgai! We'll check it out in the coming days :)

[rishabmamgai]

Hi @andrewtavis, I just finished testing CI workflow. Tried to explore testing locally with act instead of using my fork. It is working well, was able to push to my remote docker repo (private) 🏌️‍♂️.

Would like to know the opinion about local testing. Also there is one thing if you could look into, whether to use bot or github account for pushing tags. Currently pushing tag gets stuck on github password auth.