Streamline OBIS download and render

[bbest]

Streamline strategy to get pages rendered with latest OBIS data

Differentiate steps using Github Actions:

• 1. Download latest OBIS records
     • OBIS download here: site_template.Rmd#L227-L250
     • We can use MEOWs as polygons
• 2. Render website using site_template.Rmd
• Similar to .github/workflows/update-oceano.yml
• Advantages:
  • Can use a Docker image to spin up server with packages loaded very quickly
  • Can do a shallow copy of the Github repo so only the latest versions of files need to get downloaded

[bbest]

Now using Github Actions here:

• .github/workflows/obis_download.yml
  • scripts/obis_download.R

[bbest]

TODO: create another script/obis_render.R to run in workflow before losing downloaded OBIS data.

[bbest]

Clicking Run workflow under Github Actions here:

https://github.com/marinebon/p2p/actions?query=workflow%3Aobis_download

Then seeing progress:

[bbest]

Yay, it worked:

Next step is to render the sites with another script in the job.

[bbest]

Hey @eqmh and @7yl4r,

The Github Action obis_download to download OBIS data and render sites is now fully working (eg run 73d5534)and set to run on the 7th day of each month:

• .github/workflows/obis_download.yml
  • scripts/obis_download.R
  • scripts/make_sites.R

Note that the make_sites.R script got moved into the scripts/ folder. I updated the .travis.yml accordingly, but this Github Action takes care of updating the SST/Chl too so think the Travis-CI method can be retired. We could setup a separate frequency with two different Github Actions, eg OBIS monthly and SST/Chl daily.