Skip to content
This repository was archived by the owner on Aug 13, 2019. It is now read-only.

Commit a16d999

Browse files
committed
Merge branch 'master' of github.com:skshetry/Chirp
2 parents 51bb085 + 371b53c commit a16d999

File tree

1 file changed

+34
-1
lines changed

1 file changed

+34
-1
lines changed

README.md

Lines changed: 34 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,34 @@
1-
Check [wiki](https://gitlab.com/TeamSPD/Chirp/wikis/home) for setup information.
1+
# ProjectChirp
2+
Project Chirp is a social networking site written using Python/Django.
3+
See demo here: https://projectchirp.herokuapp.com/
4+
5+
## Installation
6+
7+
1. Create a postgres database named `chirp` with you as an `owner`.
8+
2. Clone this repo(preferably use ssh clone instead of https, you won't be bothered asking for password every time you push/pull).
9+
- `git clone [email protected]:skshetry/Chirp.git`
10+
3. `cd` into this repo(where you cloned) and create a virtual environment(preferably, using `python -m venv venv` on `bash`/`zsh`).
11+
12+
On Windows if above didn't work, `c:\Python36\python -m venv c:\path\to\venv`.^[[1](https://docs.python.org/3/library/venv.html)]
13+
4. Activate the virtual environment( `source venv/bin/activate`).
14+
15+
On Windows, either use `venv\Scripts\activate.bat` on `cmd.exe` or `venv\Scripts\Activate.ps1`on `PowerShell`(default on Windows 10).
16+
5. Install all the requirements (`pip install -r requirements/local.txt`).
17+
18+
If this didn't work, use `python -m pip install -r requirements/local.txt`.
19+
6. Copy the file `env.example` from root of the repo in a new file `.env`(dot env) in the same directory.
20+
Don't delete `env.example` though.
21+
7. Open the file and change the `<user>` to the database `owner` and `<pass>` to the database password.
22+
8. Make migrations file and migrate.
23+
- ~~`./manage.py makemigrations`~~
24+
- `./manage.py migrate`
25+
9. Run test to ensure everything is working.
26+
- `./manage.py test`
27+
28+
If it doesn't, revisit all the above points. It might be that you have forgotten something along the way.
29+
10. Run the development server.
30+
- `./manage.py runserver`
31+
11. Open the repo in your favorite text editor.
32+
12. Before you start working, create a issue and corresponding WIP(Work in Progress) branch and merge request(MR) from gitlab.
33+
34+
Pull that using `git pull --all` and checkout to the new branch(`git checkout <branchname>`).

0 commit comments

Comments
 (0)