Gergő Jedlicska
638969cd01
* yarn first go * fix frontend build cache loader * yarn workspaces built server Docker * build(yarn): add workspaces plugin config * chore(package defs): clean package*.json -s * chore(gitignore): ignore yarn error log * build(yarn): update yarn lock * build(preview-service webpack): add extra resolved path to preview service webpack config because of yarn package hoisting, there are no package level node_modules folder anymore. * build(docker): update dockerignore with yarn specific configs * build(docker): update Dockerfiles for yarn workspaces utilization * ci(circleci): update server test job to yarn * ci(circle): disable cache restore * ci(circleci): trying the node orb yarn-run * ci(circleci): yarn-run again * ci(circleci): disable node orb * ci(circleci): change base node image for tests * ci(circleci): add yarn cache * ci(circleci): remove node install step * ci(circleci): add server specific cache archives * ci(circleci): test build and publish * ci(circleci): change npm auth method to suit yarn * ci(circleci): trying new builder image * ci(circleci): another base image, maybe this works * ci(circleci): force a specific docker engine version * ci(circleci): add yarn version plugin and its changes * ci(circleci): cleanup and remove temp branch config * chore(package defs): moving from npm run to yarn * explicitly specifying webpack4 as a frontend dep * chore(package defs): replace npm with yarn everywhere * docs(root readme): update with some yarn specific docs * chore(root workspace): update dev scripts and package lock * ci(circleci): enable package publish step with yarn Co-authored-by: Fabians <fabis94@live.com>
78 lines
4.5 KiB
Markdown
78 lines
4.5 KiB
Markdown
# Speckle Server
|
|
|
|
[](https://twitter.com/SpeckleSystems) [](https://speckle.community) [](https://speckle.systems) [](https://speckle.guide/dev/)
|
|
|
|
#### Status
|
|
|
|
[](https://github.com/Speckle-Next/SpeckleServer/) [](https://codecov.io/gh/specklesystems/speckle-server)
|
|
[](https://results.pre-commit.ci/latest/github/specklesystems/speckle-server/main)
|
|
|
|
## Disclaimer
|
|
|
|
We're working to stabilize the 2.0 API, and until then there will be breaking changes.
|
|
|
|
## Documentation
|
|
|
|
Comprehensive developer and user documentation can be found in our:
|
|
|
|
#### 📚 [Speckle Docs website](https://speckle.guide/dev/)
|
|
|
|
## Introduction
|
|
|
|
The Speckle Server is a node application tested against v12.
|
|
|
|
The external dependencies are **PostgreSQL** and **Redis**. To get the dependencies running without any hassle, you can run them in docker containers as described in our [Server deployment instructions](https://speckle.guide/dev/server-setup.html#step-1-set-up-dependencies) (chapter `Run your speckle-server fork`, step 1)
|
|
|
|
> **_NOTE:_** If you install PostgreSQL yourself or use an existing PostgreSQL instance, make sure to create a database and a user that can access it
|
|
|
|
After you have PostgreSQL and Redis running, in the `packages/server` folder:
|
|
|
|
- copy the `.env-example` file to `.env`,
|
|
- (if you plan to run tests) copy the `.env.test-example` file to `.env.test`
|
|
- If you have a custom setup, open and edit the `.env` & `.env.test` files, filling in the required variables,
|
|
- run `yarn install`,
|
|
- finally `yarn dev`,
|
|
- check `localhost:3000/graphql` out!
|
|
|
|
## Developing
|
|
|
|
The server consists of several semi-related components, or modules. These can be found in `/modules`. Module composition:
|
|
|
|
- an `index.js` file that exposes two functions, `init` and `finalize` (mandatory)
|
|
- a `graph` folder, with two subfolders, namely `resolvers` and `schemas` (optional - these will be picked up and merged).
|
|
|
|
## Server & Apps
|
|
|
|
### Frontend
|
|
|
|
- In **development** mode, the Speckle Server will proxy the frontend from `localhost:3000` to `localhost:8080`.
|
|
If you don't see anything, ensure you've run `yarn dev` in the frontend package.
|
|
|
|
- In **production** mode, the frontend is served by an `nginx` container that proxy server requests to the server (depending on the requested path). For more information about making a production deployment, check out [our detailed guide](https://speckle.guide/dev/server-setup.html)
|
|
|
|
### GraphIQL
|
|
|
|
A GraphIQL app is available for authenticated api exploration at `localhost:3000/explorer`. Note that for the authentication flow to work, you need to have the frontend running first.
|
|
|
|
### GraphQL Playground
|
|
|
|
For non-authenticated api exploration, you can use the Graphql Playground which is available by default at `localhost:3000/graphql`.
|
|
|
|
## Testing
|
|
|
|
To run all tests, simply run `yarn test`.
|
|
The recommended extensions for the workspace include a test explorer, that can run individual tests.
|
|
|
|
If you really want to run specific tests from a terminal, use the `mocha --grep @subset` syntax. For example:
|
|
|
|
- `mocha --grep @auth --watch` to run tests pertaning to the auth module only in watch mode.
|
|
- `mocha --grep @core-streams --watch` to run tests pertaining to stream related services.
|
|
|
|
## Community
|
|
|
|
The Speckle Community hangs out on [the forum](https://speckle.community), do join and introduce yourself & feel free to ask us questions!
|
|
|
|
## License
|
|
|
|
Unless otherwise described, the code in this repository is licensed under the Apache-2.0 License. Please note that some modules, extensions or code herein might be otherwise licensed. This is indicated either in the root of the containing folder under a different license file, or in the respective file's header. If you have any questions, don't hesitate to get in touch with us via [email](mailto:hello@speckle.systems).
|