|Steven vanZyl 9154d51939 Fix some bugs||2 days ago|
|.circleci||2 months ago|
|.github||3 months ago|
|migrations||3 weeks ago|
|scripts||2 months ago|
|src||2 days ago|
|static||3 months ago|
|templates||3 weeks ago|
|.dockerignore||2 months ago|
|.gitignore||3 months ago|
|CONTRIBUTING.md||4 months ago|
|Cargo.toml||2 months ago|
|DEPLOYING.md||3 months ago|
|Dockerfile||2 months ago|
|LICENSE||5 months ago|
|README.md||2 months ago|
|Rocket.toml||2 days ago|
|diesel.toml||5 months ago|
|logo.svg||1 month ago|
Rewrite of the RCOS observatory in a way that hopefully makes a bit more sense. Since we have kinda lost track of what number we’re on at this point I am codenaming this version Observatory-New (I think it’s the 5th version though).
This implementation is intended to be simpler than previous incarnations in order to be easier to maintain in the long run.
If you would like to help out please read CONTRIBUTING.md.
Before anything else make sure that you have the development tools for your system. On Ubuntu/Debian you can install these with:
$ sudo apt install build-essential pkg-config
Then you need to install the
openssl development headers.
How to do this varies by system but on Ubuntu the package is
libssl-dev and should be similar on other distros.
Next install Rust with Rustup. Instructions are on the website linked and is fairly straightforward.
Rocket requires Rust Nightly (for now).
However the Rust official tooling does not support the generic
so I suggest using the latest dated version of
nightly that the RLS
supports. You can check that on this page
and can install it with the following command. Make sure to run this in the
$ rustup override set nightly-YYYY-MM-DD
You have to manually keep this up to date, so every week or so run the command a gain with a newer date.
After that it’s as simple as
$ cargo build
And to run do
$ cargo run
This is for deploying to a server, not a developer machine
Please read the Deploying instructions for information on how to setup and deploy observatory-new.
The code is primarily documented using in-code doc comments. This can be viewed either by browsing the source or in a web browser with.
$ cargo doc --no-deps --document-private-items --all-features --open