create a deployment workflow #26

New issue

Closed

opened 2025-10-17 23:00:48 +00:00 by AndreFerreira5 · 2 comments

AndreFerreira5 commented

2025-10-17 23:00:48 +00:00

(Migrated from github.com)

this workflow should only run whenever code is merged into the main branch.
it should comprise of a trigger to the chosen backend hosting service for deployment

choose a backend hosting service for deployment

this workflow should only run whenever code is merged into the main branch. it should comprise of a trigger to the chosen backend hosting service for deployment - [x] choose a backend hosting service for deployment

AndreFerreira5 commented

2025-10-17 23:32:05 +00:00

(Migrated from github.com)

Render will be used, for now, as the backend hosting service

[Render](render.com) will be used, for now, as the backend hosting service

AndreFerreira5 commented

2025-10-17 23:36:21 +00:00

(Migrated from github.com)

render automatically detects changes on the main branch and deploys, so the workflow stays on hold for now.
if, in the future, another deploy option appears, this issue must be reopened

render automatically detects changes on the main branch and deploys, so the workflow stays on hold for now. if, in the future, another deploy option appears, this issue must be reopened

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

AndreFerreira5/starranja#26

No description provided.

Rows
Columns