# .gitlab-ci.yml
image: alpine:latest
only on branches:
rules:
-
tags are normally used to discribe versions
-
working mostly like git tags
-
BUT have the same issue like git tag as that it is a changeable reference, although normally one should not change such tag reference
- in reality though we have observed it multiple times that the underlying image to a tag changed
- assumption in some cases was, that a fixup or similar was applied backwards
- but this broke enough deployments for us to show an issue
-
a possible solution:
- (official definition): Kubernetes is a portable, extensible, open source platform for managing containerized workloads and services, that facilitates both declarative configuration and automation.
- insimpler terms: it's a container orchestrator (which mainly manages containers)
- it support a distributed cluster architecture
- where a cluster describes a collection of multiple nodes/server (normally 3/5/7... consensus relevant)
- as it useses, to store the cluster state, the
etcd
distributed key-value store, which under the hood uses the Raft consensus algorithm - with that it manages containers across the cluster, so across all the nodes
- it normally is used distributed but also can run as a single node instance, mostly for development purpose
#!/bin/bash | |
##### BEGIN SETTINGS ##### | |
SYSTEM=debian | |
ARCH=armhf | |
SUITE=testing | |
DEVICE=image.bin | |
HOSTNAME=unknown |
docker-compose
-
everything you learn you actually already know
- it's absolutly the same as with just docker
- only difference is, it's more declerative
-
let's learn and compare pure docker vs docker-compose
agenda
cors (Cross-origin resource sharing)
- cors en wiki
Certain "cross-domain" requests, notably Ajax requests, are forbidden by default by the same-origin security policy. CORS defines a way in which a browser and server can interact to determine whether it is safe to allow the cross-origin request.[3] It allows for more freedom and functionality than purely same-origin requests, but is more secure than simply allowing all cross-origin requests.
- related to: Same-origin_policy
- cors wildcard only works WITHOUT credentials, @see_fetch_api, @see_fetch_request_api
- fetch spec