You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-26Lines changed: 3 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,41 +6,18 @@ Forti is a REST webservice that delivers weather and ocean forecast timeseries d
6
6
7
7
The data sources to the service are irregular grids of data, produced by batch jobs. These batch jobs use a wide range of input datasets, and run a set of post-processing algorithms to both improve the forecast quality and to add additional forecast parameters.
8
8
9
-
The application is built with Go, although with some small parts in C++.
9
+
The application is built with Go, although with some small parts in C++. It is meant to be run as containers — each component has an associated Dockerfile.
10
10
11
11
The code for the batch jobs that produce the datasets are not included in this repository.
12
12
13
-
## Usage
13
+
## Getting started
14
14
15
-
The application is meant to be run as containers. Each component has an associated Dockerfile.
15
+
[Getting started guide](docs/getting-started.md)
16
16
17
17
## Development
18
18
19
19
### Test
20
20
21
-
### Build
22
-
23
-
For all components, except fortiup, a docker image is built and pushed on every commit.
24
-
They will all get the same tag, corresponding to the GitHub Actions `run_id`, which identifies a single workflow run.
25
-
26
-
For example, you may end up with the following images in the registry.
0 commit comments