V1 migration / intergration #2

New Issue

cowch · 2025-02-14T07:30:04-06:00

cowch commented

2025-02-14 07:30:04 -06:00

As we will run both v1 backend and front end. And v2 at the same time when we do nightly builds we want to be able to control if we stop v1 and if a full thing has been moved to v2 remove the process from v1. To keep it all seamless.

Auth first then full front end move to v2 and just update the calls :) using vite proxy

As we will run both v1 backend and front end. And v2 at the same time when we do nightly builds we want to be able to control if we stop v1 and if a full thing has been moved to v2 remove the process from v1. To keep it all seamless. Auth first then full front end move to v2 and just update the calls :) using vite proxy

cowch added this to the lstv2 project 2025-02-14 07:30:04 -06:00

cowch commented

2025-02-23 18:56:37 -06:00

we will be putting v2 onto port 3001 first to make sure we can run both until the entire frontend if done with current features, dayton to get the first go as ill be there.

cowch moved this to Enhancements in lstv2 on 2025-02-23 18:56:51 -06:00

cowch closed this issue

2025-06-10 15:03:25 -05:00

cowch moved this to Closed in lstv2 on 2025-06-10 16:27:35 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cowch/lstV2#2