blob: a9d44bc74eec9bc8b1232c7a40fa3c2bc8d8e845 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
# Personal-site README
To get a pretty version of this document, run
$ markdown README > README.html
## License
See LICENSE file.
## Authors
See AUTHORS file.
## Dependencies
- python
- python-virtualenv
## Python dependencies
More detail in `requirements.txt` and `requirements_prod.txt`; it is best to
use virtualenv and pip to handle these. But if you insist on (Arch GNU/Linux)
packages, you will probably want the following:
- django
- python-markdown
- python-memcached
## Testing Installation
1. Clone personal-site
$ git clone https://git.sr.ht/~heckyel/personal-site
2. Run `virtualenv`.
$ cd personal-site && virtualenv ./venv/
3. Activate the virtualenv.
$ source ./venv/bin/activate
4. Install dependencies through `pip`.
$ pip install -r django/requirements.txt
5. Copy `settings.py.example` to `settings.py` and modify.
Make sure to uncomment the appropriate database section (either sqlite or
PostgreSQL).
$ cp -v django/personalsite/settings.py.example django/personalsite/settings.py
6. Check syntax.
$ python django/manage.py check --deploy
7. Migrate changes.
$ python django/manage.py migrate
8. Create superUSER
$ python django/manage.py createsuperuser
9. Use the following commands to start a service instance
$ python django/manage.py runserver
## Production Installation
The [HACKING.md](HACKING.md) file helps the deployment in production
|
