@@ -26,15 +26,15 @@ newgrp docker
26
26
```
27
27
28
28
All the commands below are being run in ` oioioi ` directory (main directory of the repository).
29
- In order to use ` easy_toolbox.py ` alternative method, check python package requirements in ` easy_toolbox.py ` .
29
+ In order to use ` easy_toolbox.py ` alternative method, check python package requirements in ` easy_toolbox.py ` .
30
30
31
- To build OIOIOI image run
31
+ To build OIOIOI image run
32
32
``` bash
33
33
OIOIOI_UID=$( id -u) docker-compose -f docker-compose-dev.yml -f extra/docker/docker-compose-dev-noserver.yml build
34
34
```
35
35
or
36
36
``` bash
37
- ./easy_toolbox.py build
37
+ ./easy_toolbox.py build
38
38
```
39
39
40
40
Set your containers up and running
@@ -103,12 +103,12 @@ As mentioned above GitHub Actions replaced most of the Hudson jobs. Right now th
103
103
- Transifex translations uploader
104
104
105
105
## Deployment
106
- No changes can be seen on ` szkopul.edu.pl ` without deployment.
106
+ No changes can be seen on ` szkopul.edu.pl ` without deployment.
107
107
@twalen is responsible for conducting the deployments, and they are usually done during
108
108
maintenance window (see ` szkopul.edu.pl ` main page for details).
109
109
110
- During deployment translation files are being uploaded and downloaded. The translation manager is
111
- [ Transifex] ( https://www.transifex.com/sio2project/sio2project/dashboard/ ) . When you add localized text
110
+ During deployment translation files are being uploaded and downloaded. The translation manager is
111
+ [ Transifex] ( https://www.transifex.com/sio2project/sio2project/dashboard/ ) . When you add localized text
112
112
to OIOIOI it is uploaded to Transifex with GitHub Action and later, when translated, downloaded,
113
113
compiled and saved to the codebase. (Both of these jobs need to be run manually).
114
114
@@ -119,20 +119,20 @@ Ticketing was moved to GitHub Issues.
119
119
## FAQ
120
120
121
121
### When to use ` ./easy_toolbox.py build ` ?
122
- Essentially, it is not easy to answer.
122
+ Essentially, it is not easy to answer.
123
123
Firstly, let's understand what each of the commands does.
124
- As you may already know, SIO2 development environment works in containerized infrastructure.
125
- We have four containers up and running, required for SIO2 to work properly.
126
- Database (` db ` ), RabbitMQ (` broker ` ), Worker (` worker ` ) and OIOIOI (` web ` ).
127
- Postgres and RabbitMQ already have existing docker images on Docker Hub.
128
- We only need to build (here comes the magic word) SIO dependent images.
129
- ` Dockerfile ` defines what steps are to be done in order to create the environment.
130
- Once you built the image, you can set the container up.
131
- Remember - things like dependencies (` requirements[_static].txt ` , ` setup.py ` ) are downloaded during the built,
132
- so if you changed something in those places you either need to build the image again,
133
- or apply these changes by hand (e.g. do ` pip install ` ).
134
- If you have good internet connection and adequate CPU, it shouldn't be hard to build the image again,
135
- especially that it is more stable approach.
124
+ As you may already know, SIO2 development environment works in containerized infrastructure.
125
+ We have four containers up and running, required for SIO2 to work properly.
126
+ Database (` db ` ), RabbitMQ (` broker ` ), Worker (` worker ` ) and OIOIOI (` web ` ).
127
+ Postgres and RabbitMQ already have existing docker images on Docker Hub.
128
+ We only need to build (here comes the magic word) SIO dependent images.
129
+ ` Dockerfile ` defines what steps are to be done in order to create the environment.
130
+ Once you built the image, you can set the container up.
131
+ Remember - things like dependencies (` requirements[_static].txt ` , ` setup.py ` ) are downloaded during the built,
132
+ so if you changed something in those places you either need to build the image again,
133
+ or apply these changes by hand (e.g. do ` pip install ` ).
134
+ If you have good internet connection and adequate CPU, it shouldn't be hard to build the image again,
135
+ especially that it is more stable approach.
136
136
137
137
### When to use ` ./easy_toolbox.py up ` ?
138
138
Whenever you don't have the containers up.
@@ -151,8 +151,8 @@ If not, check the output of `docker ps -a` and `docker logs <container_name>`.
151
151
### When to use ` ./easy_toolbox.py run ` ?
152
152
Whenever you want the Django web service to be running.
153
153
In development environment we use dev server, so it should catch all changes in the code.
154
- You can have the server running all the time - just make sure,
155
- that Django discovered your changes
154
+ You can have the server running all the time - just make sure,
155
+ that Django discovered your changes
156
156
(the server will restart with appropriate message like "detected changes in file ` xyz.py ` ").
157
157
158
158
### What to do when I get permission denied error?
0 commit comments