- Dec 19, 2023
-
-
Antoine R. Dumont authored
This adapts the configuration accordingly. Refs. swh/infra/sysadm-environment#5194
-
Antoine R. Dumont authored
So some views are better cached in different instances. Refs. swh/infra/sysadm-environment#5183
-
Antoine R. Dumont authored
-
Vincent Sellier authored
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5192
-
- Dec 18, 2023
-
-
Antoine R. Dumont authored
It's around 90% use of memory currently. Refs. swh/infra/sysadm-environment#5183
-
Antoine R. Dumont authored
Align with current moma settings. Refs. swh/infra/sysadm-environment#5183
-
Antoine R. Dumont authored
So we can reach https://webapp1.internal.softwareheritage.org/graphql/ as we did for the cassandra webapp [1] This avoids touching the existing instance which is wired for the actual production https://archive.softwareheritage.org/graphql/ (this is wired internally differently for now). [1] https://webapp-cassandra.internal.softwareheritage.org/graphql/ Refs. swh/infra/sysadm-environment#5183
-
- Dec 15, 2023
-
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5183
-
- Dec 14, 2023
-
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5183
-
Antoine R. Dumont authored
This reverts commit e2ddbc64.
-
Antoine R. Dumont authored
This should allow to reach the graphql through the usual https://webapp1.internal.softwareheritage.org/graphql/ endpoint. Refs. swh/infra/sysadm-environment#5183
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5183
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5183
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5183
-
Vincent Sellier authored
-
- Dec 13, 2023
-
-
Antoine R. Dumont authored
This now allows to provide optionally a journal writer configuration (for read-only configuration, this is not needed). Refs. swh/infra/sysadm-environment#5183
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5183
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5183
-
Antoine R. Dumont authored
It was using the staging ranges. Refs. swh/infra/sysadm-environment#5183
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5183
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5183
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5179
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5179
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5179
-
-
-
- Dec 12, 2023
-
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5179
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5179
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5179
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5179
-
Antoine R. Dumont authored
In staging, we don't have any static history data. Refs. swh/infra/sysadm-environment#5179
-
Guillaume Samson authored
-
Antoine R. Dumont authored
As mentioned in the plan, it should not have been activated. There is no history on the staging instance. Refs. swh/infra/sysadm-environment#5179
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5179
-
Antoine R. Dumont authored
Refs. swh/infra/sysadm-environment#5179
-
Guillaume Samson authored
Related to swh/infra/sysadm-environment#5165
-
Guillaume Samson authored
Related to swh/infra/sysadm-environment#5165
-
Guillaume Samson authored
Related to swh/infra/sysadm-environment#5165
-
Guillaume Samson authored
Related to swh/infra/sysadm-environment#5165
-