search

gbif / hosted-portals

Support material for establishing the GBIF Hosted Portals
Apache License 2.0
9 stars 6 forks source link

"Hosted by GBIF" footer bar for hosted portals #222

Closed javiesgm closed 2 years ago

javiesgm commented 2 years ago

It is necessary to include a footer bar with a "Hosted by GBIF" sign The bar should be dark grey #1A1A1A and 70px height.

Here is the .svg hosted-by-gbif

And here is a mockup hosted-by-70px

It should include a link to a GBIF.org page, but I'm still working on it. In the meantime, please link to this news item: https://www.gbif.org/news/6RG9WSU3knIxyhcDUBQTJY/first-five-hosted-portals-emerge-from-gbif-pilot-programme

MortenHofft commented 2 years ago

To be shown in production, the sites needs to get a new release. For some sites that could take months. The alternative is that we create a nonsense release for each site. Or better - that we add a way to do a production deployment from Jenkins (or even just as a script)

MattBlissett commented 2 years ago

This is one option, but it releases the most recent commit which isn't necessarily what we want (e.g. most recent commit of PBIF is broken), other sites might have commits that aren't ready for release.

curl -X POST -d 'payload={"action":"published"}' -i 'https://builds.gbif.org/job/hp-north-america/buildWithParameters?token=XXX'

(Or with {"action":"published"} pasted into "Build with parameters" in Jenkins.)

MortenHofft commented 2 years ago

Exactly - what I want is to rebuild and deploy the last release. In the past I have checked out the last release commit and then released that anew (I think that was the procedure), but it is fairly time consuming and awkward.

Whenever I update the theme I essentially want to do this.

Another approach I've used is to click through past builds until I find something that looks like a release. And then copy paste the payload to a new build. But that also require a lot of searching and clicking in hope of finding the last releaes. Which can at times be far back

MortenHofft commented 2 years ago

Hmm - I've tried the approach with going back to past jobs in Jenkins and cp the payload. That worked in the sense that they all got the new footer.

BUT, as I did it for sprep it failed. Which makes me think that it isn't doing what I thought it would do - namely use the tag to deploy a new version. But simply takes head. Else I do not see why SPREP would fail. In that case it means that I have most likely deployed head for all the sites. Which wasn't what I wanted at all.

UPDATE: I can confirm that is indeed the case. The Legume site hasn't been released since March 10, but I have just deployed head to prod. This is very frustrating.

javiesgm commented 2 years ago

Please update the footer link to https://gbif.org/hosted-portals

javiesgm commented 2 years ago

:)