Starting VFP migration setup dev environment

Looking to make sure we are starting off with the correct foundation.

We will be converting several VFP apps
each application uses the same underlying database (DBF's)
each app has multiple users across the network
data is currently on a shared drive on our NAS
there is cache data at a second location and live data across the vpn

Looking to understand the structure for install, best practice.
We will have at least 2 likely more developers working on the conversion.

We have a development sandbox with stations setup for development and testing. We have all the peripherals setup and running within the VFP app in the test environment.

We need to maintain the VFP apps and data, running concurrent when we move each module into the production environment

Currently using virtual tables and a test app, we have successfully added, deleted and modified records while VFP was open and working.

Our next step is to get the dev instance setup

GITHUB - how can I point this to a specific folder, it is defaulting to my user profile root, cant have this.

We then need the shared data folder F:\Fox\Data to setup our virtual tables, our devs will substitute the f drive in dev as needed. We do not have live data in the dev environment.

1. Use a project to hold the 3 applications.

2. Gitkaken makes Git user easier.

Hi Ron,

That all sounds fine as long as you aren’t developing on the live VFP data.

What are you referring to re GitHub? Please explain.

https://www.lianja.com/doc/index.php...ersion_Control
I found this article referencing GitHub to support multiple developers.

What I am looking to answer;
have you had any issues over a vpn, table access with virtual tables.

how do we setup lianja virtual tables programmatically, and where is the path to them.

When we merge the code back into the base and start testing, are the virtual tables created on the fly. We want to be able to work the files locally or from the nas.

What is the best way multiple developers to work within Lianja on several systems together, assume that was GitHub was for. Take the environment to the local PC, then merge it back into the codebase. Since you have github within your system I assume that is the solution. If there is a recommended way I want to know before we get started.

We are looking for any advice to keep us from going down the wrong path. this is a clean slate and we are all new to lianja. If you had to start from zero knowing what you know what would you do to get the right start.

Hi Ron,

See
https://www.lianja.com/doc/index.php..._to_Repository

You can assign work to different developers and have them submit versioned packages into your development repository.

This allows you to roll changes back and forward into your development environments.

Regarding VTs, if your database only contains VTs and no native data you can include the database in these packages.

Packages may contain a setup.prg or upgrade.prg. If this exists it is run when the pakage is installed.
https://www.lianja.com/doc/index.php...ackage_Manager

The CREATE/ALTER VIRTUALTABLE command can be used to programatically created VTs if required.
https://www.lianja.com/doc/index.php/ALTER_VIRTUALTABLE