aursu

Concepts

Security Guide - Chapter 5. Using Firewalls

aursu

Distributing files via Bintray includes three steps: creating a version, uploading the files and publishing the files.

1. Creating a version: Uploaded files are associated with a specific version of a package. Some upload methods can create the version automatically as part of the upload; with other methods you will need to create a target version from the Bintray UI or using REST.

2. Uploading: Upload your files using one of the methods described in the "Uploading" section. After uploading your files, the files have a status of "un-published". This means that in the Bintray UI they are only visible to you and can only be downloaded with your username and API Key. You may discard all or some of your uploaded files when they are "un-published", before anyone sees or downloads them.

aursu

For more information about downloading using APIs, please see the documentation.

This is what you need to do to resolve RPM artifacts from Bintray:

1. Run the following to get a generated .repo file:

   wget https://bintray.com/aursu/custom/rpm -O bintray-aursu-custom.repo
   

aursu

#!/bin/sh

interface=$1

if [ "$2" = "up" -a -f /etc/sysconfig/network-scripts/ifcfg-$interface ]; then
   /usr/sbin/ip link set dev $1 mtu 1390
fi

aursu

#!/bin/bash

set -e

APPROOT=/var/www/answerhub
BKPSUF=$(date +%Y-%m-%d:%H:%M)
PERM="tomcat:tomcat"
STOPCMD="systemctl stop tomcat"
STARTCMD="systemctl restart tomcat"

aursu

#version=DEVEL
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all
# Shutdown after installation
shutdown
# Use text mode install
text --non-interactive
repo --name="koji-override-0" --baseurl=http://kojipkgs.fedoraproject.org/compose/28/Fedora-28-20180425.0/compose/Everything/$basearch/os

aursu

#circleci

• Running Docker Commands
• Configuring CircleCI
• Configuring CircleCI - jobs

A run is comprised of one or more named jobs. Jobs are specified in the jobs map. The name of the job is the key in the map, and the value is a map describing the job.

If you are using Workflows, jobs must have a name that is unique within the .circleci/config.yml file.

aursu

https://docs.docker.com/registry/
https://docs.docker.com/registry/introduction/
https://docs.docker.com/registry/deploying/

GitHub:
https://github.com/docker/distribution

aursu

log_format gitlab_access '$remote_addr - $remote_user [$time_local] "$request_method $filtered_request_uri $server_protocol" $status $body_bytes_sent "$filtered_http_referer" "$http_user_agent"';
log_format gitlab_mattermost_access '$remote_addr - $remote_user [$time_local] "$request_method $filtered_request_uri $server_protocol" $status $body_bytes_sent "$filtered_http_referer" "$http_user_agent"';


# Remove private_token from the request URI
# In:  /foo?private_token=unfiltered&authenticity_token=unfiltered&rss_token=unfiltered&...
# Out: /foo?private_token=[FILTERED]&authenticity_token=unfiltered&rss_token=unfiltered&...
map $request_uri $temp_request_uri_1 {
  default $request_uri;
  ~(?i)^(?<start>.*)(?<temp>[\?&]private[\-_]token)=[^&]*(?<rest>.*)$ "$start$temp=[FILTERED]$rest";

aursu

#  http://nginx.org/en/docs/http/websocket.html
map $http_upgrade $connection_upgrade {
  default upgrade;
  ''      close;
}