What is the best way to manage development with Fusio?

[kidino]

Once I have Fusio all set up, I would be uploading and updainge PHP files in the /src folder for the classes I created. With a normal web project, I would normally create a webhook and Git setup where I can just push the new codes.

But with Fusio, while I can do development locally to test my API, going into production, I would have to upload/update my classes in /src folder and then create the routes for my API again. Then create/update my tables if required.

I do see the the command line utility (bin/fusio) has the system:import and system:export command. But I assume that creates adds the data into the DB for the routes, actions and other data.

I guess generally I am asking how best to work with Fusio with a development and production setup, with easy deployment?

[chriskapp]

Hi, so the for this we have the php bin/fusio deploy command which you can run after you have updated all your classes in the src/ folder. It then creates all routes etc. which you have defined at the resources/ folder. Fusio parses these .yaml files and uses the internal API to create theses items. Note this does not execute any migrations, if you use the migration system at src/Migrations/System then you have to manually call the command php bin/fusio migration:migrate --connection=System to execute all missing migrations on your database.