Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy include source files #554

Open
chriskapp opened this issue May 11, 2024 · 0 comments
Open

Deploy include source files #554

chriskapp opened this issue May 11, 2024 · 0 comments

Comments

@chriskapp
Copy link
Member

Currently you can use the deploy system to automatically create all Fusio resources i.e. operstiona, actions, schemas etc. from a GIT repository. Therefor you only need to describe those resources at .yaml files and then you can use the php bin/fusio deploy command to push those changes to your Fusio instance. This has the great advantage that you can put your complete Fusio configuration under version control and you can easily create a new Fusio instance with the same settings.

The deploy system currently does not updates source files i.e. if your operation references a custom action class in the src/ folder Fusio will not deploy this class from the src folder instead it will only create the operation. If you deploy this to a remote server it will result in an error since the action class does not exist on the server. It would be great if the deploy command would also provide a way to send all src/ files (and probably also the resources/container.php) to a remote Fusio instance. Maybe we can also think about the composer.json and vendor/ dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant