search

shortbread-tiles / shortbread-docs

Documentation of the Shortbread vector tile schema
https://shortbread-tiles.org
Creative Commons Zero v1.0 Universal
28 stars 6 forks source link

Add CI job for build&deploy #62

Closed pka closed 2 months ago

pka commented 2 months ago

As the domain name and SSL is already set up, we could use it e.g. for an 1.1 branch preview.

flohoff commented 2 months ago

Ich wollte das im staging branch zusammenpuzzeln und dann ggfs die commits mergen beim branch merge. Ich habe exakt sowas jetzt in den staging branch gepackt. Kann nur den secret key nicht parken weil ich dafür nicht dir rechte habe.

Ich kann ja keinen shortbread-tiles.org webserver mit SSL bauen bis nicht der DNS record umgezogen ist. Und DNS record umziehen und dann stundenlang basteln fand ich doof. Deshalb staging. Wenn es nicht genutzt wird kann es ja anschliessend wieder weg.

pka commented 2 months ago

@joto I haven't enough permissions for setting the ssh key secret. Can you (at least temporarely) upgrade my role?

pka commented 2 months ago

I've temporarely set the SSH_KEY used for main branch deployment to the staging user, so CI currently deploys main and staging to https://staging.shortbread-tiles.org/

flohoff commented 2 months ago

So we are now using MAIN and the staging key to deploy to staging? The idea was to get everything working in the staging branch and adding a second key for main. Then change DNS records, setup a new Webserver and get an SSL certificate and at the same time merge staging to main, which would then automatically deploy to the correct production web server.

So whats the plan now?

Are we gonne reuse the same key (Which is not possible from the rrsync target as the sync target is bound to the key so we now need to manually switch over ssh/authorized keys and paths) or are we generating a new key and we need to coordinate to switch over the key in github?