Servers and databases
The Servers panel (Ctrl+1, ⌘1 on macOS) lists the instances on your computer first, then your saved connections to other Galactus servers. Each is one line: a status mark, its name and its port or address. The one you are working with is highlighted, with its databases listed beneath it.
Hover a row to see its buttons, or right-click it for every action.
Instances on your computer
An instance is a data folder with one database, plus the system database that holds its
users and roles. Keep one per project: each has its own data, its own database name and its
own gdb password.
- Make one: + Add › New local instance…, then give it a name and a database name. The database is created the first time the instance starts.
- Start and stop: ▶ and ■ on the row, or Start server on the Server view.
- One at a time: all instances share the Bolt port, so your applications always connect
to
bolt://127.0.0.1:7687. Starting another instance asks before stopping the running one, and says how many clients are connected to it. - Rename: press F2 over the row, double-click the instance in use, or right-click › Rename. Stop the instance first: renaming moves its data folder and its saved passwords.
- Delete: × on the row. Station asks you to type the instance's name, because its
database goes with it. The data folder moves to
deletedinside Station's folder rather than being erased.
The square beside the name shows the state: hollow when stopped, lime while running, blue with a spinner while starting or stopping, red when the server has stopped with an error. The error itself shows in red under the row.
Station runs Galactus DB 2.0, so every instance stores its graph on the
Paged engine. An instance made by Station 0.3 or earlier moves to
it the first time Station 0.4 starts it: Station first dumps the database to a
pre-upgrade-…gdb file in the backup folder beside its data, then opens it on the new
engine. A large database
takes about a minute; a small one, under a second.
Station listens on 127.0.0.1, so programs on your computer connect to it. For a database
that other machines and containers share, run Galactus DB with Docker
or on a server, and add it here as a connection.
Connections to other servers
+ Add offers three kinds: Local Docker, Galactus Cloud and Remote. Each
fills in sensible defaults; enter the address, user and password, then Test and save.
Addresses use bolt:// or, with TLS, bolt+s://. For a server whose certificate comes from
your own certificate authority, give the CA file as a PEM bundle.
Tick Remember the password to keep it in your operating system's credential store. Otherwise Station keeps it only until you close the window.
Click a connection to work with it. Its diamond is lime once connected, spins while connecting, and turns red if the server cannot be reached, with the reason under the row. Right-click › Edit… changes its details; × removes it, and the message in the corner offers Undo for a few seconds. A removed connection's saved password leaves the credential store once Undo has passed.
Choosing a database
The server you are working with lists its databases under its row. Click one to send the current query tab's queries there; the editor shows the database's name above the query, and clicking that name brings you back to this panel. Right-click a database for Browse data or Schema graph, each in a new query tab.
A server with more than eight databases gets a filter box above the list. F5 refreshes the list and the schema.
Arranging the sidebar
Instances and connections stay in the order you give them:
- Drag a row up or down. A line shows where it will land.
- Or right-click it › Move up / Move down.
The same works for snippet collections and snippets; see Snippets and history.