http://www.ox-holdings.com

前言XMPP开源IM客户端Spark近日发布了2.8新匍京娱乐场官方下载:.2版,Openfire安装和使用都非常简单

摘要XMPP开源IM顾客端Spark近期发表了2.8.2版,该版本是个独立发表版,首要是修复了一部分Bug并扩张了LittleLuck界凉粉肤。前言XMPP开源IM顾客端斯Parker近来公布了2.8.2版,该版本是个单身宣布版,首如果修补了有些Bug并追加了LittleLuck界凉皮肤。斯Parker是叁个开源、跨平台IM顾客端(补助Linux、windows、Mac OS X平台)。它的个性帮忙集组谈天,电话集成和强大安全性能。要是集团中间布署IM使用Openfire+斯帕克是精品的整合。官方的验证原来的书文This is a regular update. But there is a change, which can affect new users. "Accept all certificates" option on the Adanced menu on the Login screen won't be enabled by default for new users from now on. This option makes 斯Parker automatically accept expired, self-signed and other incorrect TLS certificates. Which makes it less secure. If you are using self-signed certificates, your new users will have to enable this option manually (once卡塔尔(قطر‎. Or you can add this option to a preconfigured spark.properties file, if you distribute it to new users. Old users won't be affected by this (those upgrading straight from 2.7 version will still be affected卡塔尔国. We encourage server admins to use certificates from trusted authorities (e.g. Let's Encrypt卡塔尔(قطر‎. This version also includes 4.1.9 update for Smack, which has a fix for a critical security vulnerability.UPDATE (二〇一六/11/39卡塔尔(قطر‎:it looks like Spark is not saving settings on Advanced menu, if a user has never opened it. For such users "Accept all certificates" setting will be disabled after updating to 2.8.2 from any version. They will have to go to Advanced menu and enable if if they encounter "Unable to verify a certificate" error.Those who are using Client Control plugin will have to update it to version 2.1.0 as 斯Parker2.8.2 is already modified to work with that version and it will miss many menus and checkboxes if being used with an older version of that plugin. 2.1.0 version requires Openfire 4.0.0 at least. If you are using older version of Openfire and want to keep using Client Control, you might want to hold of updating to Spark2.8.2.(官方原来的书文: 版更新内容Bug:[SPARK-1516] - Spark should not let open profile edit by clicking the avatar if profile changing is disabled[SPARK-1520] - Systray icon changes to online when one opens the chat window[SPARK-1593] - Spark shouldn't add Offline status when a user goes invisible[SPARK-1758] - Unfiled group appears when contact goes online[SPARK-1801] - Fix links opening in KDE environment (updated)[SPARK-1816] - Shouldn't freeze when using unsupported plugins[SPARK-1820] - Can't switch back to online presence after turning invisible on[SPARK-1827] - Shouldn't allow broadcast to selected users when it is disabled in Client Control新功能:[SPARK-1802] - Add LittleLuck skin[SPARK-1835] - Modify Spark to work with new Openfire Client Control plugin settings杂项:[SPARK-1732] - Update bundled JRE with the latest version[SPARK-1837] - Update Smack to the latest version (4.1.9)优化:[SPARK-1021] - Default to Name field as nickname when adding a contact[SPARK-1434] - Add Polish Spelling option[SPARK-1789] - Change Accept all certificates option to disabled by default[SPARK-1822] - Add additional default properties to control GUI settings[SPARK-1824] - Update Polish translation[SPARK-1831] - Update Italian translation越来越多版本更新记录,请参见:

摘要Openfire发表4.1.5版,Openfire 接收Java开采,开源的实时同盟(RTC)服务器基于XMPP(Jabber)公约。Openfire安装和利用都特别轻便,并接收Web实行田间管理。单台服务器可帮衬上万并发客户。前言Openfire基于XMPP(Jabber)合同,采纳Java开辟,是开源的即时通信(IMState of Qatar服务器。Openfire安装和动用都特别轻易,并动用Web实行田间管理,单台服务器可支撑上万并发顾客。Openfire开采组织表示将接二连三大力营造一个平安无事的4.1本子各样,肃清自 4.1.0 发行版以来在 Openfire 中遇见的roster group难点等。4.1.5版更新内容Bug[OF-1310] - Can`t delete last item of the pubsub node[OF-1327] - Should not compare incomparable types[OF-1330] - Can't enable database query statistics on the admin console[OF-1332] - Update bundled MySQL driver to fix utf8mb4 databases[OF-1334] - Monitoring Plugin displays "Archive index rebuild failed"[OF-1348] - AuthBased*Provider try to use SortedSet without Comparable items[OF-1355] - UserImportExport plugin: import should not fail when optional config is missingTask[OF-1343] - Update install guide about the automatic service installationImprovement[OF-1277] - Change setting name to Invisible Login and Status[OF-1325] - Implement separate History settings in Client Control[OF-1326] - Allow BOSH context to be re-used.[OF-1338] - Minimum server version restrictions should ignore release status identifier[OF-1341] - Windows Launcher requires to run "as administrator"[OF-1342] - Remove "Run Openfire" from the final step of the installer[OF-1347] - Group settings update[OF-1350] - Be less strict when setting a password on a MUC room[OF-1351] - Parse 'release' number[OF-1352] - Plugin version number should not wrap官方链接:

Linking to MySQL Container

You can link this image with a mysql container for the database requirements. The alias of the mysql server container should be set to mysql while linking with the gitlab image.

If a mysql container is linked, only the DB_ADAPTERDB_HOST and DB_PORT settings are automatically retrieved using the linkage. You may still need to set other database connection parameters such as the DB_NAMEDB_USERDB_PASS and so on.

To illustrate linking with a mysql container, we will use the sameersbn/mysql image. When using docker-mysql in production you should mount a volume for the mysql data store. Please refer the README of docker-mysql for details.

First, lets pull the mysql image from the docker index.

docker pull sameersbn/mysql:latest

For data persistence lets create a store for the mysql and start the container.

SELinux users are also required to change the security context of the mount point so that it plays nicely with selinux.

mkdir -p /srv/docker/gitlab/mysql
sudo chcon -Rt svirt_sandbox_file_t /srv/docker/gitlab/mysql

The run command looks like this.

docker run --name gitlab-mysql -d 
    --env 'DB_NAME=gitlabhq_production' 
    --env 'DB_USER=gitlab' --env 'DB_PASS=password' 
    --volume /srv/docker/gitlab/mysql:/var/lib/mysql 
    sameersbn/mysql:latest

The above command will create a database named gitlabhq_production and also create a user named gitlab with the password password with full/remote access to the gitlabhq_production database.

We are now ready to start the GitLab application.

docker run --name gitlab -d --link gitlab-mysql:mysql 
    --volume /srv/docker/gitlab/gitlab:/home/git/data 
    sameersbn/gitlab:8.5.1

Here the image will also automatically fetch the DB_NAMEDB_USER and DB_PASS variables from the mysql container as they are specified in the docker run command for the mysql container. This is made possible using the magic of docker links and works with the following images:

  • mysql
  • sameersbn/mysql
  • centurylink/mysql
  • orchardup/mysql

External Redis Server

The image can be configured to use an external redis server. The configuration should be specified using environment variables while starting the GitLab image.

Assuming that the redis server host is 192.168.1.100

docker run --name gitlab -it --rm 
    --env 'REDIS_HOST=192.168.1.100' --env 'REDIS_PORT=6379' 
    sameersbn/gitlab:8.5.1

Crowd

To enable the Crowd server OAuth2 OmniAuth provider you must register your application with Crowd server.

Configure GitLab to enable access the Crowd server by specifying the OAUTH_CROWD_SERVER_URLOAUTH_CROWD_APP_NAME andOAUTH_CROWD_APP_PASSWORD environment variables.

Twitter

To enable the Twitter OAuth2 OmniAuth provider you must register your application with Twitter. Twitter will generate a API key and secret for you to use. Please refer to the GitLab documentation for the procedure to generate the API key and secret with twitter.

Once you have the API key and secret generated, configure them using the OAUTH_TWITTER_API_KEY andOAUTH_TWITTER_APP_SECRET environment variables respectively.

For example, if your API key is xxx and the API secret key is yyy, then adding --env 'OAUTH_TWITTER_API_KEY=xxx' --env 'OAUTH_TWITTER_APP_SECRET=yyy' to the docker run command enables support for Twitter OAuth.

Issues

Docker is a relatively new project and is active being developed and tested by a thriving community of developers and testers and every release of docker features many enhancements and bugfixes.

Given the nature of the development and release cycle it is very important that you have the latest version of docker installed because any issue that you encounter might have already been fixed with a newer docker release.

Install the most recent version of the Docker Engine for your platform using the official Docker releases, which can also be installed using:

wget -qO- https://get.docker.com/ | sh

Fedora and RHEL/CentOS users should try disabling selinux with setenforce 0 and check if resolves the issue. If it does than there is not much that I can help you with. You can either stick with selinux disabled (not recommended by redhat) or switch to using ubuntu.

You may also set DEBUG=true to enable debugging of the entrypoint script, which could help you pin point any configuration issues.

If using the latest docker version and/or disabling selinux does not fix the issue then please file a issue request on the issuespage.

In your issue report please make sure you provide the following information:

  • The host distribution and release version.
  • Output of the docker version command
  • Output of the docker info command
  • The docker run command you used to run the image (mask out the sensitive bits).

Deploy to a subdirectory (relative url root)

By default GitLab expects that your application is running at the root (eg. /). This section explains how to run your application inside a directory.

Let's assume we want to deploy our application to '/git'. GitLab needs to know this directory to generate the appropriate routes. This can be specified using the GITLAB_RELATIVE_URL_ROOT configuration option like so:

docker run --name gitlab -it --rm 
    --env 'GITLAB_RELATIVE_URL_ROOT=/git' 
    --volume /srv/docker/gitlab/gitlab:/home/git/data 
    sameersbn/gitlab:8.5.1

GitLab will now be accessible at the /git path, e.g. http://www.example.com/git.

NoteThe GITLAB_RELATIVE_URL_ROOT parameter should always begin with a slash and SHOULD NOT have any trailing slashes.

Redis

GitLab uses the redis server for its key-value data store. The redis server connection details can be specified using environment variables.

Linking to Redis Container

You can link this image with a redis container to satisfy gitlab's redis requirement. The alias of the redis server container should be set to redisio while linking with the gitlab image.

To illustrate linking with a redis container, we will use the sameersbn/redis image. Please refer the README of docker-redis for details.

First, lets pull the redis image from the docker index.

docker pull sameersbn/redis:latest

Lets start the redis container

docker run --name gitlab-redis -d 
    --volume /srv/docker/gitlab/redis:/var/lib/redis 
    sameersbn/redis:latest

We are now ready to start the GitLab application.

docker run --name gitlab -d --link gitlab-redis:redisio 
    sameersbn/gitlab:8.5.1

Installation

Automated builds of the image are available on Dockerhub and is the recommended method of installation.

Note: Builds are also available on Quay.io

docker pull sameersbn/gitlab:8.5.1

You can also pull the latest tag which is built from the repository HEAD

docker pull sameersbn/gitlab:latest

Alternatively you can build the image locally.

docker build -t sameersbn/gitlab github.com/sameersbn/docker-gitlab

Internal Redis Server

The internal redis server has been removed from the image. Please use a linked redis container or specify a external redisconnection.

OmniAuth Integration

GitLab leverages OmniAuth to allow users to sign in using Twitter, GitHub, and other popular services. Configuring OmniAuth does not prevent standard GitLab authentication or LDAP (if configured) from continuing to work. Users can choose to sign in using any of the configured mechanisms.

Refer to the GitLab documentation for additional information.

Strengthening the server security

This section provides you with instructions to strengthen your server security. To achieve this we need to generate stronger DHE parameters.

openssl dhparam -out dhparam.pem 2048

Prerequisites

Your docker host needs to have 1GB or more of available RAM to run GitLab. Please refer to the GitLab hardware requirementsdocumentation for additional information.

External Issue Trackers

Since version 7.10.0 support for external issue trackers can be enabled in the "Service Templates" section of the settings panel.

If you are using the docker-redmine image, you can one up the gitlab integration with redmine by adding --volumes-from=gitlab flag to the docker run command while starting the redmine container.

By using the above option the /home/git/data/repositories directory will be accessible by the redmine container and now you can add your git repository path to your redmine project. If, for example, in your gitlab server you have a project namedopensource/gitlab, the bare repository will be accessible at /home/git/data/repositories/opensource/gitlab.git in the redmine container.

Facebook

To enable the Facebook OAuth2 OmniAuth provider you must register your application with Facebook. Facebook will generate a API key and secret for you to use. Please refer to the GitLab documentation for the procedure to generate the API key and secret.

Once you have the API key and secret generated, configure them using the OAUTH_FACEBOOK_API_KEY andOAUTH_FACEBOOK_APP_SECRET environment variables respectively.

For example, if your API key is xxx and the API secret key is yyy, then adding --env 'OAUTH_FACEBOOK_API_KEY=xxx' --env 'OAUTH_FACEBOOK_APP_SECRET=yyy' to the docker run command enables support for Facebook OAuth.

郑重声明:本文版权归新匍京a奥门-最全网站手机版app官方下载所有,转载文章仅为传播更多信息之目的,如作者信息标记有误,请第一时间联系我们修改或删除,多谢。