You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
poetry run bash -c 'source setup_env.sh && flask run-worker'
62
+
```
63
+
64
+
Open your browser to: **http://127.0.0.1:5000/taiga/**
65
+
66
+
You are automatically logged in as the seeded admin user (`admin@broadinstitute.org`) via the `DEFAULT_USER_EMAIL` setting.
67
+
68
+
Without S3 configured, you can browse/search the seeded data, create folders, and work with the UI. File uploads require either MiniStack or real AWS credentials (see below).
69
+
70
+
## Local S3 with MiniStack (Optional)
71
+
72
+
[MiniStack](https://github.com/Nahuel990/ministack) is a free, open-source AWS emulator that runs 33 AWS services (including S3 and STS) in a single Docker container. It lets you test the full upload pipeline locally without an AWS account.
73
+
74
+
### Setup
75
+
76
+
1. Start MiniStack:
77
+
78
+
docker run -d --name ministack -p 4566:4566 nahuelnucera/ministack
Set `S3_ENDPOINT_URL = ''` and clear the AWS keys in`settings.cfg`. The app runs fine without S3 — you just can't upload files.
108
+
109
+
## Configuring AWS (Production)
37
110
38
111
We need two users: One IAM account (main) is used in general by the app to read/write to S3. The second (uploader) has it's rights delegated via STS on a short term basis. However, this user should
39
112
only have access to upload to a single location within S3.
40
113
41
114
Permissions for the main user:
42
115
43
-
```{
116
+
```json
117
+
{
44
118
"Version": "2012-10-17",
45
119
"Statement": [
46
120
{
@@ -57,7 +131,8 @@ Permissions for the main user:
57
131
58
132
Permissions for the "upload" user:
59
133
60
-
```{
134
+
```json
135
+
{
61
136
"Version": "2012-10-17",
62
137
"Statement": [
63
138
{
@@ -112,46 +187,13 @@ For our case, it is pretty simple:
112
187
113
188
#### Configure Taiga to use your Bucket
114
189
115
-
1. Copy `settings.cfg.sample` to `settings.cfg`
116
-
2. edit `settings.cfg` and set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
117
-
3. also set S3_BUCKET to the bucket created above
118
-
119
-
## Installing
120
-
121
-
1. Install all the dependencies:
122
-
123
-
`poetry install`
124
-
`poetry shell`
125
-
126
-
2. Create a test database to have some data to work with:
127
-
128
-
`./flask recreate-dev-db`
190
+
1. Edit `settings.cfg` and set`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`
191
+
2. Set `S3_BUCKET` to the bucket created above
192
+
3. Remove `S3_ENDPOINT_URL` (or leave it empty) so the app connects to real AWS
129
193
130
-
3. Open 4 terminal windows to launch Webpack, Taiga 2, Celery and Redis processes:
194
+
## Adding user to admin group
131
195
132
-
a. In terminal 1:
133
-
134
-
`./flask webpack`
135
-
136
-
b. In terminal 2:
137
-
138
-
`redis-server`
139
-
140
-
c. In terminal 3:
141
-
142
-
`./flask run`
143
-
144
-
d. In terminal 4:
145
-
146
-
`./flask run-worker`
147
-
148
-
4. Congratulations! You can now access to Taiga 2 through your browser at:
149
-
150
-
`http://127.0.0.1:5000/taiga/`
151
-
152
-
## adding user to admin group
153
-
154
-
```
196
+
```sql
155
197
INSERT INTO group_user_association (group_id, user_id) select1, id FROM users WHERE name =
0 commit comments