UNPKG

atom-nuclide

Version:

A unified developer experience for web and mobile development, built as a suite of features on top of Atom to provide hackability and the support of an active community.

nuclide.io

facebook/nuclide

66 lines (45 loc) • 2.18 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
# nuclide-server Provides a collection of services that are run on the Nuclide server to support remote file editing. This runs as a Node package to provide the server-side functionality required by Nuclide to support remote file editing. ## Nuclide Server Prerequisites * **[Node](https://nodejs.org) v0.12.0 or greater**. There are various installer and package options depending on your platform on the [nodejs.org site](https://nodejs.org/download/). * **[Watchman](https://facebook.github.io/watchman)**. The Nuclide server requires Watchman to detect file and directory changes. You can build and/or install Watchman for your server's platform as described [here](http://facebook.github.io/watchman/docs/install.html#build-install). * **SSH Daemon**. The Nuclide client connects to the server via SSH, so ensure that the server exposes an SSH daemon that you can connect to from your client machine, and that you know the credentials required. ## Installing Nuclide Server Ensure that the Nuclide project is checked out onto the remote server. Run the following command from the root of the repository to install Nuclide's server dependencies: ``` ./scripts/dev/setup --no-atom ``` Note that the `--no-atom` flag ensures that only Nuclide's Node packages are installed on the server, and not those used by the Atom client itself. ## Running Nuclide Server You do not need to explicitly start the server since the Nuclide client will attempt to do so when it first connects over SSH, as explained in [Remote Projects README](../remote-projects/README.md). ## Troubleshooting If you want to debug the server starting up, you can of course run the command directly: ``` ./pkg/nuclide-server/nuclide-start-server ``` A successful start will display the port upon which the server has started, and a JSON dump of certificate information: ``` Nuclide started on port 9090. {"workspace": null, "ca": "-----BEGIN CERTIFICATE-----\n... ``` The `nuclide-start-server` command also has a useful help option: ``` ./pkg/nuclide-server/nuclide-start-server -h ``` This explains many of the other options available, such as timeout, workspace directory to use and so on.