update ci actions
This commit is contained in:
@@ -0,0 +1,35 @@
|
|||||||
|
name: Build and Push to Digital Ocean Container Registry
|
||||||
|
|
||||||
|
on:
|
||||||
|
push:
|
||||||
|
branches: [main]
|
||||||
|
|
||||||
|
jobs:
|
||||||
|
build-and-push:
|
||||||
|
runs-on: actions-server
|
||||||
|
|
||||||
|
steps:
|
||||||
|
- name: Checkout
|
||||||
|
uses: actions/checkout@v4
|
||||||
|
|
||||||
|
- name: Install doctl
|
||||||
|
run: |
|
||||||
|
curl -sL https://github.com/digitalocean/doctl/releases/latest/download/doctl-linux-amd64.tar.gz | tar xz
|
||||||
|
sudo mv doctl /usr/local/bin
|
||||||
|
|
||||||
|
- name: Auth with DOCR
|
||||||
|
run: |
|
||||||
|
doctl auth init -t "${{ secrets.DO_TOKEN }}"
|
||||||
|
doctl registry login
|
||||||
|
|
||||||
|
- name: Build image
|
||||||
|
run: |
|
||||||
|
docker build --platform linux/amd64 \
|
||||||
|
-t registry.digitalocean.com/radiantwave-portal-container-registry/portal:${{ gitea.sha }} \
|
||||||
|
-t registry.digitalocean.com/radiantwave-portal-container-registry/portal:latest \
|
||||||
|
.
|
||||||
|
|
||||||
|
- name: Push image
|
||||||
|
run: |
|
||||||
|
docker push registry.digitalocean.com/radiantwave-portal-container-registry/portal:${{ gitea.sha }}
|
||||||
|
docker push registry.digitalocean.com/radiantwave-portal-container-registry/portal:latest
|
||||||
@@ -1,10 +1,31 @@
|
|||||||
# Rhema Wave Technologies - User Portal
|
# Radiant Wave Technologies - User Portal
|
||||||
|
A combination application that combines the main Radiant Wave API with a user-facing account management application,
|
||||||
Everything you need to build a Svelte project, powered by [`sv`](https://github.com/sveltejs/cli).
|
and an admin-facing platform management application. An all-in-one management platform for Radiant Wave and Radiant Wave Technologies.
|
||||||
|
|
||||||
## Deployment
|
## Deployment
|
||||||
|
This application runs inside of a Docker container, defined by the Dockerfile found within this repo.
|
||||||
|
Codeberg/Gitea actions are triggered on `push` actions to the `main` branch, and build the docker container.
|
||||||
|
The docker container is then uploaded to the Digital Ocean Container Registry, where it is pulled into an
|
||||||
|
App Platform application and run.
|
||||||
|
|
||||||
- Update the Authorized Redirect URIs on Google Cloud Console
|
To build the Docker container locally (with podman), ensuring builds pass prior to pushing to `main`:
|
||||||
- Update the Better Auth URL
|
|
||||||
- To migrate development changes to the database, run `npm run migarte -- <migration_name>`
|
```sh
|
||||||
- To run deployment changes to the database, run `npm run deploy`
|
podman build --platform linux/amd64 -t registry.digitalocean.com/radiantwave-portal-container-registry/portal:latest .
|
||||||
|
```
|
||||||
|
|
||||||
|
To build the Docker container on a Linux machine, such as a Forgejo Action Runner:
|
||||||
|
|
||||||
|
```sh
|
||||||
|
docker build -t registry.digitalocean.com/radiantwave-portal-container-registry/portal:latest .
|
||||||
|
```
|
||||||
|
|
||||||
|
Then push to the container registry:
|
||||||
|
|
||||||
|
```sh
|
||||||
|
podman push registry.digitalocean.com/radiantwave-portal-container-registry/portal:latest
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Development
|
||||||
Reference in New Issue
Block a user