jmarya/knowledge
jmarya/knowledge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

refactor

Browse source
This commit is contained in:
JMARyA 2023-12-22 00:39:15 +01:00
parent 95cdf40e4c
commit 5ed8bcb4b3
Signed by: jmarya
GPG key ID: 901B2ADDF27C2263
3 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
technology/applications/SSH.md
View file

@ -83,6 +83,7 @@ Host myserver
Hostname server-address Hostname server-address
Port port Port port
IdentityFile ~/.ssh/id_rsa IdentityFile ~/.ssh/id_rsa
User you
ProxyJump host ProxyJump host
ProxyCommand corkscrew <proxy-host> <proxy-port> %h %p # HTTP Proxy ProxyCommand corkscrew <proxy-host> <proxy-port> %h %p # HTTP Proxy
``` ```

2
technology/applications/package managers/Flatpak.md
View file

@ -20,7 +20,7 @@ Runtimes are collections of libraries and services that applications can use. Fl
A Flatpak ref is a specific version of a runtime or an application. It is identified by a unique hash, allowing multiple versions to coexist on a system. A Flatpak ref is a specific version of a runtime or an application. It is identified by a unique hash, allowing multiple versions to coexist on a system.
## Usage ## Usage
#refactor #refactor #notnow
```shell ```shell
flatpak install <app> # Install applications flatpak install <app> # Install applications
flatpak update # Update applications flatpak update # Update applications

2
technology/tools/Docker Compose.md
View file

@ -368,7 +368,7 @@ secrets:
``` ```
## Docker Compose Deploy ## Docker Compose Deploy
The Compose Deploy Specification lets you declare additional metadata on services so Compose gets relevant data to allocate adequate resources on the platform and configure them to match your needs. The Compose Deploy Specification lets you declare additional metadata on services so Compose gets relevant data to allocate adequate resources on the platform and configure them to match your needs. [Docker Swarm](Docker%20Swarm.md) respects these specifications.
### `mode` ### `mode`
`mode` defines the replication model used to run the service on the platform. Either `global`, exactly one container per physical node, or `replicated`, a specified number of containers. The default is `replicated`. `mode` defines the replication model used to run the service on the platform. Either `global`, exactly one container per physical node, or `replicated`, a specified number of containers. The default is `replicated`.