Separate env for designer #13461

framitdavid · 2024-09-03T10:00:10Z

We should separate the env for the designer, to support auto-deploy to prod after PR is merged to main.

mirkoSekulic · 2024-09-04T07:53:21Z

mirkoSekulic · 2024-09-10T10:02:18Z

@framitdavid this can be moved to done since you updated docs right?

framitdavid added this to Team Studio Sep 3, 2024

framitdavid converted this from a draft issue Sep 3, 2024

framitdavid added the added-to-sprint label Sep 3, 2024

framitdavid changed the title ~~Seperate env for designer~~ Separate env for designer Sep 3, 2024

framitdavid changed the title ~~Separate env for designer~~ Separate env for designer backend Sep 3, 2024

framitdavid changed the title ~~Separate env for designer backend~~ Separate env for designer Sep 3, 2024

mirkoSekulic moved this from 📈 Todo to 👷 In Progress in Team Studio Sep 4, 2024

mirkoSekulic self-assigned this Sep 4, 2024

mirkoSekulic mentioned this issue Sep 10, 2024

feat: designer cd #13466

Merged

4 tasks

mirkoSekulic closed this as completed Sep 10, 2024

github-project-automation bot moved this from 👷 In Progress to Documentation in Team Studio Sep 10, 2024

mirkoSekulic moved this from Documentation to ✅ Done in Team Studio Sep 10, 2024

Provide feedback