commit
ad7ba38e11
|
@ -1,10 +1,10 @@
|
|||
version: '3.7'
|
||||
version: "3.7"
|
||||
|
||||
services:
|
||||
sia:
|
||||
environment:
|
||||
- JAEGER_DISABLED=${JAEGER_DISABLED:-true} # Enable/Disable tracing
|
||||
- JAEGER_SERVICE_NAME=${PORTAL_NAME:-Skyd} # change to e.g. eu-ger-1
|
||||
- JAEGER_DISABLED=${JAEGER_DISABLED:-true} # Enable/Disable tracing
|
||||
- JAEGER_SERVICE_NAME=${PORTAL_NAME:-Skyd} # change to e.g. eu-ger-1
|
||||
# Configuration
|
||||
# See https://github.com/jaegertracing/jaeger-client-go#environment-variables
|
||||
# for all options.
|
||||
|
@ -16,7 +16,11 @@ services:
|
|||
|
||||
jaeger-agent:
|
||||
image: jaegertracing/jaeger-agent
|
||||
command: [ "--reporter.grpc.host-port=jaeger-collector:14250", "--reporter.grpc.retry.max=1000" ]
|
||||
command:
|
||||
[
|
||||
"--reporter.grpc.host-port=jaeger-collector:14250",
|
||||
"--reporter.grpc.retry.max=1000",
|
||||
]
|
||||
container_name: jaeger-agent
|
||||
restart: on-failure
|
||||
expose:
|
||||
|
|
|
@ -4,4 +4,4 @@ outlined in the README in the root directory, under "Setting up CockroachDB".
|
|||
The only difference between the files here and those under
|
||||
`docker/cockroach/certs` is that the files here need to be readable by anyone, while the files under `cockroach` need to
|
||||
have their original access rights
|
||||
(all *.key files should be 600 instead of 644 there).
|
||||
(all \*.key files should be 600 instead of 644 there).
|
||||
|
|
|
@ -397,6 +397,7 @@ server {
|
|||
|
||||
# proxy /skynet/tus requests to siad endpoint with all arguments
|
||||
proxy_pass http://siad;
|
||||
proxy_redirect https://siad/ https://$domain.$tld/;
|
||||
}
|
||||
|
||||
location /skynet/metadata {
|
||||
|
|
|
@ -37,9 +37,8 @@ export default function SelfServiceForm({ flow, config, fieldsConfig, title, but
|
|||
"border-gray-300 placeholder-gray-400 focus:ring-green-500 focus:border-green-500": !Boolean(
|
||||
field?.messages?.length
|
||||
),
|
||||
"border-red-300 text-red-900 placeholder-red-300 focus:ring-red-500 focus:border-red-500": Boolean(
|
||||
field?.messages?.length
|
||||
),
|
||||
"border-red-300 text-red-900 placeholder-red-300 focus:ring-red-500 focus:border-red-500":
|
||||
Boolean(field?.messages?.length),
|
||||
}
|
||||
)}
|
||||
/>
|
||||
|
|
|
@ -3,6 +3,7 @@
|
|||
This package contains useful scripts for managing a Skynet Webportal.
|
||||
|
||||
## Available Scripts
|
||||
|
||||
**blocklist-skylink.sh**\
|
||||
The `blocklist-skylink.sh` script adds a skylink to the blocklist on all
|
||||
servers.
|
||||
|
@ -29,11 +30,12 @@ The `portal-upgrade.sh` script upgrades the docker images for a portal and
|
|||
clears and leftover images.
|
||||
|
||||
## Webportal Upgrade Procedures
|
||||
|
||||
TODO...
|
||||
|
||||
1. 1 server upgraded at a time
|
||||
1. Clusters of servers upgraded at a time
|
||||
1. How to safetly revert to previous stable version. Document what those
|
||||
versions were.
|
||||
1. Upgrading single subsystem
|
||||
1. Upgrading multiple subsystems
|
||||
|
||||
|
|
Reference in New Issue