JetBrains Space Help

Administration of Space On-Premises

There are several administration activities specific only to Space On-Premises:

  1. Uploading a Space product license.

  2. Enabling push notification for mobile clients.

  3. Updating Space On-Premises.

  4. Migrating from Space On-Premises EAP.

Otherwise, in terms of administration, Space On-Premises is no different from its cloud version – refer to Administrator's Guide for basic administration instructions.

Upload a Space product license

  1. In a browser, open your clean Space On-Premises installation. In case of a proof-of-concept installation, the default URL is http://127.0.0.1:8084.

  2. Under the License field, click the link to log in to your JetBrains Acccount.

  3. On your account page, copy the license string and return back to Space.

  4. Paste the string to the License field.

  5. Fill other fields if required and click Get started.

Enable push notifications for mobile clients

Space provides mobile clients for iOS and Android. To send push notifications to mobile clients, your Space On-Premises instance must use a proxy server from JetBrains. The proxy server delivers the notifications to end users through the corresponding Apple and Google services.

To enable the proxy server for push notifications

  1. Make sure your Space instance has access to https://on-premise.service.jetbrains.space.

  2. On the navigation bar, click administration.png Administration and choose Notifications Proxy.

  3. Choose JetBrains Proxy and click Save.

Update Space On-Premises

Space On-Premises supports only forward updates – it's not possible to downgrade to previous versions. The update procedure requires downtime because of the data migration. Make sure to plan the maintenance window and inform your users about the upcoming activities.

Migrate from Space On-Premises EAP

If you used Space On-Premises 2021.1 EAP, it may be possible to transfer all your data to a new 2022.1 Beta installation. If the PostgreSQL and MinIO/S3-compatible storage are configured as external services in your EAP installation, you can simply continue using them.

Note that in 2022.1 Beta, you must configure Elasticsearch and Redis as external services. We don't recommend that you transfer their data: Redis stores only temporary data, while the Elasticsearch index can be easily recreated.

  1. Configure Elasticsearch and Redis as external services.

  2. Reuse the corresponding database and storage configuration from your old values.yaml in the new one.

  3. Stop the Space 2021.1 EAP instance and deploy the 2022.1 version with the updated values.yaml.

  4. Wait for Space to finish the internal database migration and initialize.

Last modified: 12 August 2022