ok staging, but I say a different thing.
I’m talking about sharing in the same local network.
If you have developed this software it is because locally you often work faster and also in situations where there is no line. But then it happens that you move to another computer, and you can’t work on the project.
Example I created the project on my 15 inch laptop and I want to continue working from the desktop computer with 30 inch monitor.
Or you can’t work with a colleague on the same local network.
Being able to share the project with the local network is very useful, because I can continue to work on the project from other computers or in a team, while remaining locally.
It’s certainly possible from within Docker but currently not a feature we offer by default on DevKinsta. This may take a bit of searching if you’re interested in making this possible with your setup. I’ve moved this thread over to our Feature Requests category if anyone else is interested in this. Thanks!
Hi, I haven’t been able to do that.
Are you planning to introduce this functionality? it is really very useful for testing on multiple devices or continuing to work from other devices with a colleague.
It would indeed be very useful if the DevKinsta solution would allow to share a project on the local network, at least for testing purposes so that a site can be tested from different devices in the network, as also pointed out by @WoodyP
In the meantime though, I’m using this solution which works for me:
Syncing code and database states with other machines can become quite complex, especially if more than one user is accessing or even changing the project at the same time.
But I think it’s possible by changing some folder locations:
You can share your project code internally by moving the DevKinsta folder to a shared network folder. All computers need to run DevKinsta and use that same folder. But I’m not sure, if there are problems when multiple machines try to access the same files at once.
→ You can customize the location of your DevKinsta folder in the DevKinsta settings (the setting is called “Site Path”)
The difficult part is, to sync the DB with all machines, as the settings of the devkinsta_db container cannot be changed. MySQL data is stored in /var/lib/docker/volumes/devkinsta_db_data/_data which is a location inside Dockers virtual machine. You could try to also move Dockers Disk Image to a network drive. Though, I can imagine that only one MySQL server can access that location at once - i.e. you can only launch DevKinsta on one machine at the same time.
→ Open Docker for Mac, click the cog icon to open the settings, in “Resources > Advanced” change the location of the “Disk Image location” and have it point to a shared network folder.
Note: Maybe can also use a symlink to have those two locations point to a network drive.
The other option is, that you use version control to commit/share code between machines. You just need to remember to commit and push your changes before starting to work on the other device. This is (in my opinion) the cleanest and safest way to avoid collisions and conflicts. The drawback is, that each machine has a different database state.