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
It describes a process used for using multiple (database) branches, which may not be relevant to implement for a two-week exploratory school project. But it does some samples of connection strings that are useful.
You can also explore the .devcontainer folder in this repo - somehow both mysql and pscale CLIs are working fine from the Codespace. It's the .devcontainer/postCreate.sh that does the trick - you can do the same in any GitHub Action runner - which means that you do run any sql scritp agains the database - from your workflow.
I also created a very simple python script: py/dbdump.py I use it to dump the DDL (schema) of a database. But you can easily make a copy - and have it make something else with your remote database. Consequently you not even needmysql or pscale in you GitHub Action Runner?
The text was updated successfully, but these errors were encountered:
PlanetScale has a quite extensive and elaborated post; Using the PlanetScale CLI with GitHub Actions workflows.
It describes a process used for using multiple (database) branches, which may not be relevant to implement for a two-week exploratory school project. But it does some samples of connection strings that are useful.
You can also explore the
.devcontainer
folder in this repo - somehow bothmysql
andpscale
CLIs are working fine from the Codespace. It's the.devcontainer/postCreate.sh
that does the trick - you can do the same in any GitHub Action runner - which means that you do run any sql scritp agains the database - from your workflow.I also created a very simple python script:
py/dbdump.py
I use it to dump the DDL (schema) of a database. But you can easily make a copy - and have it make something else with your remote database. Consequently you not even needmysql
orpscale
in you GitHub Action Runner?The text was updated successfully, but these errors were encountered: