fixed S3 policy

README.md

@@ -2,20 +2,20 @@
 
 `mc admin user add <server_alias> splitpro <secret_key>`
 `mc mb <server_alias>/splitpro`
-Bucket user policy `policy.json`: 
+Bucket user `policy.json`: 
 ```json
 {
-  "Version": "2012-10-17",
+    "Version": "2012-10-17",
   "Statement": [
-    {
-      "Effect": "Allow",
+      {
+          "Effect": "Allow",
       "Action": ["s3:ListBucket"],
       "Resource": ["arn:aws:s3:::splitpro"]
     },
     {
-      "Effect": "Allow",
+        "Effect": "Allow",
       "Action": [
-        "s3:GetObject",
+          "s3:GetObject",
         "s3:PutObject",
         "s3:DeleteObject"
       ],
@@ -26,3 +26,18 @@ Bucket user policy `policy.json`:
 ```
 `mc admin policy create <server_alias> splitpro-rw policy.json`
 `mc admin policy attach <server_alias> splitpro-rw --user splitpro`
+Bucket `anonymous_policy.json`:
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Effect": "Allow",
+      "Principal": "*",
+      "Action": "s3:GetObject",
+      "Resource": "arn:aws:s3:::splitpro/*"
+    }
+  ]
+}
+```
+`mc anonymous set-json anonymous_policy.json <server_alias>/splitpro`

compose.yml

@@ -10,7 +10,8 @@ services:
       NEXTAUTH_URL: "https://splitpro.urmel.de"
       HOSTNAME: "0.0.0.0" # Fixes implemenntatiion bug where only hostname would be used to accept connections
       DEFAULT_HOMEPAGE: "/balances"
-      ENABLE_SENDING_INVITES=: true
+      ENABLE_SENDING_INVITES: true
+      DISABLE_EMAIL_SIGNUP: true
       FROM_EMAIL: "${FROM_EMAIL}"
       EMAIL_SERVER_HOST: mail.postale.io
       EMAIL_SERVER_PORT: 465
@@ -22,9 +23,6 @@ services:
       R2_BUCKET: "splitpro"
       R2_SECRET_KEY: "${S3_SECRET}"
       R2_ACCESS_KEY: "splitpro"
-
-    ports:
-      - 3000:3000
     depends_on:
       - splitpro_db
     networks: