generated from datadiversitylab/project-template
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathOwncloud.YAML
121 lines (109 loc) · 4.02 KB
/
Owncloud.YAML
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
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
version: "3.9"
services:
redis:
image: redis
command:
- /bin/sh
- -c
- redis-server --requirepass redispass
- --databases 1
container_name: ownCloud-REDIS
hostname: owncloud-redis
mem_limit: 256m
mem_reservation: 50m
cpu_shares: 768
security_opt:
- no-new-privileges:true
read_only: true
user: 1026:100
healthcheck:
test: ["CMD-SHELL", "redis-cli ping || exit 1"]
volumes:
- /volume1/docker/owncloud/redis:/data:rw
environment:
TZ: Europe/Bucharest
restart: on-failure:5
db:
image: mariadb:11.3-jammy
command: ["--max-allowed-packet=128M", "--innodb-log-file-size=64M"]
container_name: ownCloud-DB
hostname: owncloud-db
mem_limit: 1g
cpu_shares: 768
security_opt:
- no-new-privileges:true
user: 1026:100
volumes:
- /volume1/docker/owncloud/db:/var/lib/mysql:rw
- /volume1/docker/owncloud/db:/etc/mysql/conf.d:rw
environment:
TZ: Europe/Bucharest
MYSQL_ROOT_PASSWORD: rootpass
MYSQL_DATABASE: owncloud
MYSQL_USER: ownclouduser
MYSQL_PASSWORD: owncloudpass
restart: on-failure:5
owncloud:
image: owncloud/server:latest
container_name: ownCloud
hostname: owncloud
mem_limit: 4g
cpu_shares: 768
security_opt:
- no-new-privileges:true
healthcheck:
test: ["CMD", "/usr/bin/healthcheck"]
interval: 30s
timeout: 10s
retries: 5
ports:
- 4660:8080
volumes:
- /volume1/docker/owncloud/data:/mnt/data:rw
- /etc/localtime:/etc/localtime:ro
environment:
OWNCLOUD_DOMAIN: localhost:8080
OWNCLOUD_TRUSTED_DOMAINS: 192.168.1.18,owncloud.yourname.synology.me
OWNCLOUD_DB_TYPE: mysql
OWNCLOUD_DB_NAME: owncloud
OWNCLOUD_DB_PREFIX: oc_
OWNCLOUD_DB_USERNAME: ownclouduser
OWNCLOUD_DB_PASSWORD: owncloudpass
OWNCLOUD_DB_HOST: owncloud-db
OWNCLOUD_ADMIN_USERNAME: marius
OWNCLOUD_ADMIN_PASSWORD: mariushosting
OWNCLOUD_MYSQL_UTF8MB4: true
OWNCLOUD_REDIS_ENABLED: true
OWNCLOUD_REDIS_HOST: owncloud-redis
OWNCLOUD_REDIS_PASSWORD: redispass
# more ENV @ https://github.com/owncloud-docker/base/blob/master/ENVIRONMENT.md
restart: on-failure:5
depends_on:
redis:
condition: service_healthy
db:
condition: service_started
# Necessary edits to code
"user", "OWNCLOUD_TRUSTED_DOMAINS", "OWNCLOUD_ADMIN_USERNAME", "OWNCLOUD_ADMIN_PASSWORD" and "TZ" have to be edited for every instance of installation and can be unique to every user
# Timezone
TZ:
1. (eg. America/Phoenix for TZ).
#IP
OWNCLOUD_TRUSTED_DOMAINS:
1.For this value, type in your NAS IP add a comma, and then add your synology.me DDNS without https:// at the beginning (eg. 192.168.1.18,owncloud.X.synology.me)
# Username
OWNCLOUD_ADMIN_USERNAME:
1. Type in own username.
#Password
OWNCLOUD_ADMIN_PASSWORD:
1. Type in own password.
# User
In order to find out the "user" value (which is composed of the User ID and Group ID in UID:GID format):
1. we needed to go to Control Panel/Task Scheduler/ Create/ Scheduled Task/ User-defined script.
2. Under the new window opened, there will be a 3 tabs (General, Schedule and Task Settings).
3. Under General, the Task field should be filled with “My UID and GID” and under User you should select your NAS user.
4. In the next tab “Schedule” select “Run on the following date” and select today’s date then select “Do not repeat”, select a time to run it.
5. On the next tab, “Task Settings” check the “Send run details by email” box and then add an email that can be reliably accessed.In the same tab, ad “id” as the user-defined script under the Run command section.
6. After doing this, press okay.
7. Go back to Control Panel/ Task Scheduler and select your newly created “My UID and GID” task then click on the “Run” tab and confirm the run.
8. An email will be sent to the one used in the previous step with both UID and GID values alongside additional information.