使用 Linux 和 Zulip 部署内部聊天服务器_AI阅读总结 — 包阅AI

For many companies, platforms like Slack are the go-to for communication and collaboration. But what if you don’t want to depend on a third party for such a service?

You might have highly sensitive information that you don’t want to be shared on a third-party server/service. If you’d prefer to keep this type of communication in-house, the likes of Slack and Microsoft Teams simply will not do.

If that kind of privacy and security is required by your company, you might want to consider a solution like Zulip.

Zulip is an open-source collaboration tool with plenty of features to help make in-house communication and collaboration not only possible but easy. Zulip includes features like:

• Message history search.
• Users.
• Channels.
• Topic-based threading.
• File sharing and storage.
• Voice and video chats.
• App integration.
• Localizations with more than 20 languages.
• Web, desktop, mobile and terminal apps.
• Expressive formatting.
• Collaborative messages.
• Keyboard shortcuts.
• Permanent message links.
• Custom emoji.
• Read receipts.
• Typing notifications.
• Send later and mark unread.
• Email notifications.
• Link previews.
• Linkifiers.
• And much more.

Check out the full Zulip feature list.

The core development team for Rust programming language uses Zulip to communicate.

Best of all, Zulip can be easily deployed on a Linux server without too much hassle. I’m going to show you how to do just that.

What You’ll Need

To deploy Zulip, you’ll need the following: a running instance of Linux, a user with sudo privileges and a fully qualified domain name pointed to the hosting server. If you want to limit usage of Zulip to in-house, you can without the domain name and simply use the IP address (which is how I’ll demonstrate).

Host-File Configuration

To begin the installation, you must map your hosting server’s IP address to a domain name. Let’s say your server IP is 192.168.1.137 and your domain is zulip.example.com. Open the hosts file with the command:

At the bottom of that file, add the following:

Save and close the file.

Update and Upgrade

Next, you’ll want to make sure your server is up-to-date. For example, if you’re using Ubuntu Server (which is what I’m using), you can run the following command to do both:

Download and Unpack Zulip

Next, we’re going to download and unpack the Zulip file. First, change into the /tmp directory with:

Now, download the latest version of the installer with:

If you find wget isn’t installed, you can install it with a command like:

When the download completes, unpack the file with:

Install OpenSSL

The next step is to install OpenSSL, which is required for the installation. Install this package with:

When this installation is completed, you’re ready to run the installer.

Running the Installer Script

There are two ways to run the installer:

• With a self-signed certificate.
• With a Let’s Encrypt certificate.

If you’ll be using a fully qualified domain name for your Zulip server, you must install it with Let’s Encrypt. If you’ll be using this in-house only (with no outside access), you can install it with a self-signed certificate.

To install with a self-signed certificate, the command is:

Where EMAIL is the email address you want associated with the admin account and HOST is the domain you configured in the host file.

If you plan on using Let’s Encrypt, the install command is:

Where EMAIL is the email address you want associated with Zulip and FQDN is your fully qualified domain name.

After launching the installation, I’d recommend you set about taking care of some other tasks because this takes some time (between 15 and 30 minutes, depending on the speed of your network and CPU).

When the installation completes, you’ll see a link in the final output. Either click that link or copy/paste it into a browser. That link will take you to the Zulip web-based installer, where you’ll first need to type an email address and click Create Organization (Figure 1).

If you receive an nginx error (that it was unable to start), make sure if you’ve installed Apache that you’d stopped and disabled that web server with:

After creating your organization, you’ll be required to create an admin account (Figure 2). After doing that, you can log into Zulip with that account and customize the server to fit the needs of your company.

Configuring Email for Zulip

You’ll also need to configure Zulip to use an SMTP server, so the service can send email notifications. To do this, open the necessary configuration file with:

In that file, look for the following lines:

Uncomment those lines (by removing the leading # character) and then configure as needed. For example, if you’ll be using Gmail’s SMTP servers, the lines would look like this:

Where GMAILADDRESS is your Gmail address.

Save and close the file.

You then must set the password for the SMTP server. Open the required configuration file with:

Look for the line:

Change PASSWORD to the password for your email account. If you’re using Gmail, you’ll need to create an app password.

Save and close the file.

Restart the Zulip service (so the changes will take effect) with the command:

And that’s it. You now have an in-house collaborative chat server up and running. Hopefully, this platform will help you migrate away from third-party, closed-source services, so you can enjoy more privacy and security for collaboration.