sudo curl -o /etc/yum.repos.d/mssql-server.repo https://packages.microsoft.com/config/rhel/7/mssql-server-preview.repo

yum install mssql-server

[[email protected] /]# /opt/mssql/bin/mssql-conf setup

[[email protected] /]# systemctl status mssql-server
● mssql-server.service - Microsoft sql Server Database Engine
   Loaded: loaded (/usr/lib/systemd/system/mssql-server.service; enabled; vendor preset: disabled)
   Active: active (running) since 一 2019-05-20 11:16:37 CST; 47s ago
     Docs: https://docs.microsoft.com/en-us/sql/linux
 Main PID: 26015 (sqlservr)
   CGroup: /system.slice/mssql-server.service
           ├─26015 /opt/mssql/bin/sqlservr
           └─26037 /opt/mssql/bin/sqlservr

5月 20 11:16:41 localhost.localdomain sqlservr[26015]: 2019-05-20 11:16:41.51 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
5月 20 11:16:41 localhost.localdomain sqlservr[26015]: 2019-05-20 11:16:41.51 Server      Dedicated admin connection support was established for listening locally on port 1434.
5月 20 11:16:41 localhost.localdomain sqlservr[26015]: 2019-05-20 11:16:41.51 spid20s     sql Server is Now ready for client connections. This is an informational message; no user action is required.
5月 20 11:16:42 localhost.localdomain sqlservr[26015]: 2019-05-20 11:16:41.99 spid9s      Starting up database ‘tempdb‘.
5月 20 11:16:42 localhost.localdomain sqlservr[26015]: 2019-05-20 11:16:42.24 spid9s      The tempdb database has 1 data file(s).
5月 20 11:16:42 localhost.localdomain sqlservr[26015]: 2019-05-20 11:16:42.28 spid16s     The Service broker endpoint is in disabled or stopped state.
5月 20 11:16:42 localhost.localdomain sqlservr[26015]: 2019-05-20 11:16:42.28 spid16s     The Database Mirroring endpoint is in disabled or stopped state.
5月 20 11:16:42 localhost.localdomain sqlservr[26015]: 2019-05-20 11:16:42.36 spid16s     Service broker manager has started.
5月 20 11:16:42 localhost.localdomain sqlservr[26015]: 2019-05-20 11:16:42.43 spid5s      Recovery is complete. This is an informational message only. No user action is required.
5月 20 11:16:45 localhost.localdomain sqlservr[26015]: 2019-05-20 11:16:45.31 spid33s     The activated proc ‘[dbo].[sp_syspolicy_events_reader]‘ running on queue ‘msdb.dbo.syspolicy_event_queue‘ output the following:  ‘Transaction (Proc...
Hint: Some lines were ellipsized,use -l to show in full.

[[email protected] /]# firewall-cmd --zone=public --add-port=1433/tcp --permanent
success

# ls -al

# ls /sys/firmware/efi/efivars

# ping -c 3 archlinux.org

# timedatectl set-ntp true

# fdisk -l

# fdisk -l /dev/sda

# fdisk /dev/sda

# mkfs.ext4 /dev/sda5

# mkfs.fat -F32 /dev/sda5

# mkfs.ext4 /dev/sda6

# mount /dev/sda5  /mnt

# mount /dev/sda6  /mnt

# mkdir -p /mnt/boot/efi

# mount /dev/sda5  /mnt/boot/efi

# vim /etc/pacman.d/mirrorlist

Server = https://mirrors.163.com/archlinux/repo/os/arch

# pacstrap /mnt base base-devel

# genfstab -U /mnt >> /mnt/etc/fstab

# arch-chroot /mnt

# pacman -S vim

# ln -sf /usr/share/zoneinfo/Asia/Shanghai /etc/localtime

# hwclock --systohc

zh_CN.UTF-8 UTF-8

 # locale-gen

LANG=en_US.UTF-8

127.0.0.1   localhost
::1         localhost
127.0.1.1   hellokitty.localdomain  hellokitty

# passwd

# useradd -m tom

# passwd tom

# pacman -S intel-ucode

# pacman -S os-prober

# pacman -S grub

# grub-install --target=i386-pc /dev/sda

# pacman -S efibootmgr

# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=ArchLinux

# grub-mkconfig -o /boot/grub/grub.cfg

# pacman -S gnome gnome-extra

# systemctl enable gdm

# exit

# reboot

本文分享自微信公众号 - Linux运维交流社区（gh_2eb939cabae1）。
如有侵权，请联系 support@oschina.cn 删除。
本文参与“OSC源创计划”，欢迎正在阅读的你也加入，一起分享。

BinderHub 安装指南

BinderHub 安装指南

BinderHub uses Helm Charts to set up the applications we’ll use in our Binder deployment. If you’re curious about what Helm Charts are and how they’re used here, see the Zero to JupyterHub guide.

Below we’ll cover how to configure your Helm Chart, and how to create your BinderHub deployment.

3.1. Preparing to install

To configure the Helm Chart we’ll need to generate several pieces of information and insert them into yaml files.

First we’ll create a folder where we’ll store our BinderHub configuration files. You can do so with the following commands:

mkdir binderhub
cd binderhub

Now we’ll collect the information we need to deploy our BinderHub. The first is the content of the JSON file created when we set up the container registry. For more information on getting a registry password, see Set up the container registry. We’ll copy/paste the contents of this file in the steps below.

Create two random tokens by running the following commands then copying the outputs.:

openssl rand -hex 32
openssl rand -hex 32

Note

This command is run twice because we need two different tokens.

3.2. Create secret.yaml file

Create a file called secret.yaml and add the following:

jupyterhub:
    hub:
      services:
        binder:
          apiToken: "<output of FIRST `openssl rand -hex 32` command>"
    proxy:
      secretToken: "<output of SECOND `openssl rand -hex 32` command>"

Next, we’ll configure this file to connect with our registry.

3.2.1. If you are using gcr.io

Add the following section to secret.yaml. Note that the first line is not indented at all:

registry:
  password: |
    <content of the JSON file downloaded earlier for the container registry from Service Accounts>
    <it will look something like the following (with actual values instead of empty strings)>
    {
    "type": "",
    "project_id": "",
    "private_key_id": "",
    "private_key": "",
    "client_email": "",
    "client_id": "",
    "auth_uri": "",
    "token_uri": "",
    "auth_provider_x509_cert_url": "",
    "client_x509_cert_url": ""
    }

Tip

• The content you put just after password: | must all line up at the same tab level.
• Don’t forget the | after the password: label.

3.2.2. If you are using Docker Hub

Update secret.yaml by entering the following:

registry:
  username: <docker-id>
  password: <password>

Note

• ``<docker-id>`` and ``<password>`` are your credentials to login to Docker Hub. If you use an organization to store your Docker images, this account must be a member of it.

3.3. Create config.yaml

Create a file called config.yaml and choose the following directions based on the registry you are using.

3.3.1. If you are using gcr.io

To configure BinderHub to use gcr.io, simply add the following to your config.yaml file:

registry:
  prefix:  gcr.io/<google-project-id>/<prefix>
  enabled: true

Note

• ``<google-project-id>`` can be found in the JSON file that you pasted above. It is the text that is in the project_id field. This is the project ID, which may be different from the project name.
• ``<prefix>`` can be any string, and will be prepended to image names. We recommend something descriptive such as binder-dev or binder-prod.

3.3.2. If you are using Docker Hub

Using Docker Hub is slightly more involved as the registry is not being run by the same platform that runs BinderHub.

Update config.yaml by entering the following:

registry:
  enabled: true
  prefix: <docker-id/organization-name>/<prefix>
  host: https://registry.hub.docker.com
  authHost: https://index.docker.io/v1
  authTokenUrl: https://auth.docker.io/token?service=registry.docker.io

Note

• ``<docker-id/organization-name>`` is where you want to store Docker images. This can be your Docker ID account or an organization that your account belongs to.
• ``<prefix>`` can be any string, and will be prepended to image names. We recommend something descriptive such as binder-dev or binder-prod.

3.4. Install BinderHub

First, get the latest helm chart for BinderHub.:

helm repo add jupyterhub https://jupyterhub.github.io/helm-chart
helm repo update

Next, install the Helm Chart using the configuration files that you’ve just created. Do this by running the following command:

helm install jupyterhub/binderhub --version=v0.1.0-85ac189  --name=<choose-name> --namespace=<choose-namespace> -f secret.yaml -f config.yaml

Note

• --version refers to the version of the BinderHub Helm Chart.
• name and namespace may be different, but we recommend using the same name and namespace to avoid confusion. We recommend something descriptive and short, such as binder.
• If you run kubectl get pod --namespace=<namespace-from-above> you may notice the binder pod in CrashLoopBackoff. This is expected, and will be resolved in the next section.

This installation step will deploy both a BinderHub and a JupyterHub, but they are not yet set up to communicate with each other. We’ll fix this in the next step. Wait a few moments before moving on as the resources may take a few minutes to be set up.

3.5. Connect BinderHub and JupyterHub

In the google console, run the following command to print the IP address of the JupyterHub we just deployed.:

kubectl --namespace=<namespace-from-above> get svc proxy-public

Copy the IP address under EXTERNAL-IP. This is the IP of your JupyterHub. Now, add the following lines to config.yaml file:

hub:
  url: http://<IP in EXTERNAL-IP>

Next, upgrade the helm chart to deploy this change:

helm upgrade <name-from-above> jupyterhub/binderhub --version=v0.1.0-85ac189  -f secret.yaml -f config.yaml

3.6. Try out your BinderHub Deployment

If the helm upgrade command above succeeds, it’s time to try out your BinderHub deployment.

First, find the IP address of the BinderHub deployment by running the following command:

kubectl --namespace=<namespace-from-above> get svc binder

Note the IP address in EXTERNAL-IP. This is your BinderHub IP address. Type this IP address in your browser and a BinderHub should be waiting there for you.

You now have a functioning BinderHub at the above IP address.

3.7. Increase your GitHub API limit

Note

Increasing the GitHub API limit is not strictly required, but is recommended before sharing your BinderHub URL with users.

By default GitHub only lets you make 60 requests each hour. If you expect your users to serve repositories hosted on GitHub, we recommend creating an API access token to raise your API limit to 5000 requests an hour.

1. Create a new token with default (check no boxes) permissions here.

2. Store your new token somewhere secure (e.g. keychain, netrc, etc.)

3. Before running your BinderHub server, run the following:

   export GITHUB_ACCESS_TOKEN=<insert_token_value_here>

BinderHub will automatically use the token stored in this variable when making API requests to GitHub. See the GitHub authentication documentation for more information about API limits.

For next steps, see Debugging BinderHub and Tear down your Binder deployment.

Confluence 6 安装指南

在你开始之前

在你开始安装 Confluence 之前，请确定你的安装环境满足 最小系统安装要求和支持的平台.

如果你计划将你的 Confluence 运行到虚拟环境下，请参考 Running Confluence in a Virtualized Environment 页面中的内容。

选择你的安装方式

有多种方式可以对 Confluence 进行安装。请针对你的安装环境选择最合适的安装方式。

请注意：我们不能对在 OS X 上安装 Confluence 提供支持。OS X 的下载文件只能用于对 Confluence 进行评估。与 Confluence 运行在支持的平台上运行一样，运行 Confluence 在 OS X 上没有任何限制。

EAR/WAR 分发包 已经不再可用（no longer available）。如果你现在运行的 Confluence 是在之前的 EAR/WAR 包安装来的，那么你需要选择使用 zip 或者归档文件（archive file）来进行安装。

https://www.cwiki.us/display/CONF6ZH/Confluence+Installation+Guide

关于MSSQL for Linux 安装指南的问题就给大家分享到这里，感谢你花时间阅读本站内容，更多关于.NET Core 安装指南 Debian 8、Arch Linux 安装指南、BinderHub 安装指南、Confluence 6 安装指南等相关知识的信息别忘了在本站进行查找喔。