Hello everyone! I'm currently working on a Laravel project, and my client has a requirement where they want to use the project both locally on their local host and on a production server. They would like the databases to stay in sync, so that any changes made in the local version automatically reflect in the remote version, and vice versa.
I wanted to ask if there is any recommended approach or tool available in Laravel that can facilitate database synchronization between the local and remote environments. I appreciate any guidance or suggestions on how to achieve this synchronization effectively.
Thank you in advance for your help!
@haris1566 You absolutely don’t want production data getting copied or synced outside of your production environment.
This can just lead to embarrassing mistakes where a developer accidentally emails live emails with a test email that may contain undesired copy that will then damage the company’s trust and reputation, not to mention it’s possibly breaking data protection laws if people are sat with data on their computers that they don’t need (or shouldn’t have) access to.
@martinbean You bring up valid concerns about synchronizing production data outside of the production environment. However, it's important to note that in my specific project, it is not intended for public use and is limited to a single user. The client faces internet connectivity issues and requires a mechanism that allows them to use the project on both the local and production environments.
Considering these unique circumstances, it becomes crucial to find a solution that addresses the client's needs while still ensuring data integrity and minimizing any potential risks. By implementing a carefully designed synchronization process, we can cater to the client's requirement for offline usage without compromising the security and privacy of the data.
I appreciate your input and would welcome any suggestions or insights on how to achieve a safe and reliable synchronization of the project data in this particular scenario.
@Haris1566 It sounds more like you want a PWA (Progressive Web App) with offline capabilities in that case, rather than maintaining two codebases in two environments (a development environment and a production environment) and syncing data between the two.
With a PWA, you’d have the app running on the device. If the network connection is lost, then the app will continue to function, and you can use a service worker to sync data back to the server when a network connection is restored.
You can read more about building PWAs and working offline here: https://web.dev/learn/pwa/offline-data/
If it is just one person that uses it, there is no need ro place it on the web at all, in that case a on prem host would be a much better choice.
Please or to participate in this conversation.