16%
21.08.2014
-Server/Path …. You could also specify a tape device or Samba file server:
BACKUP_URL=tape:///dev/nst0, ...
BACKUP_URL=cifs://Samba-Server/Path ...
If ReaR authenticates according to CIFS/Samba, the administrator
16%
05.12.2014
Intune enterprise account. Later in the Intune integration wizard sequence, you will be prompted to state which mobile endpoint platforms you want to support. The choices are Windows Phone 8.0/8.1, Windows
16%
17.06.2017
source license (Apache 2.0) in an irregular series of versions every few months. In early 2017, version 1.13 saw the 13th release appear since version 1.0 was published in June 2014.
In early March
16%
07.04.2022
the number of desired container machines to be created. The names of the created container machines are a combination of the cluster name, the machines name, and the count index starting from 0. The image
16%
20.06.2022
that can be deployed on both 4G and 5G technology. A 5G campus network is designed to meet special requirements (e.g., to allow Industry 4.0 [1] applications to communicate). The market for 5G campus
16%
20.06.2022
.4'
02 services:
03 keycloak:
04 container_name: keycloak
05 image: quay.io/keycloak/keycloak:17.0.1
06 ports:
07 - 8080:8080
08 environment:
09 - KEYCLOAK
16%
02.08.2022
because access tokens in the OAuth 2.0 standard are usually only valid for one hour, after which you need to obtain a new token, which involves an in-depth reappraisal of the access context. At the end
16%
22.05.2023
OS and Linux, use the binaries for your choice of OS. By default, the web interface can be accessed on https://127.0.0.1:3333/
. The username is admin
, and the password is output on the console. Before you can
16%
03.12.2015
the remote controller at 127.0.0.1:6633
. In other words, the control plane is missing. Just to confirm this, try to ping host h3 from host h1. You will see a message telling you that the host is not reachable
16%
10.06.2015
. The current version is Mesos 0.21.
Two years after the first release, the developers presented a far more advanced variant [3] at a 2011 Usenix conference. Twitter engineers had already been running Mesos
