Add create-project to cli

[jasny]

Feature request to expose the createProject method to the command line interface.

It would be useful to add a create-method command. Having to browse to insight.sensiolabs.com is a bit of a burden. Adding a project from the shell would be nice. Also maybe integrating it into IDEs like PHPStorm.

php insight.phar create-project \
  --repository-url=http://github.com/jasny/assetic-extensions \
  --type=php-library

[lyrixx]

Hello @jasny

Would you mind submit a pull request ?

Thanks.

[jasny]

@lyrixx Normally not. But as sensiolabs insight is no longer freely available for open-source projects and has a 5 project limit for a basic plan, it's not usable for me. I create micro-libraries and have dozens of those.

[tgalopin]

Hello Arnold,

I will have a look at this next week.

Note that if you have multiple small libraries, I would recommend you to use a single main repository with subtree splits. This would ease your maintenance a lot as well as allow you to analyze all your libraries at once using SensioLabsInsight basic plan.

Best regards,

[jasny]

I don't think that's a good way of structuring components as you get a monolith project (also for ci). Using composer, micro-libraries are the way to go imho. Beyond that, I also use micro-services for my projects, so it will never hold up. Limiting a plan by the number of repositories is ruling out people that prefer a micro-architecture. Not cool...

[tgalopin]

Thanks for your feedback.

I still think having a single main repository is the best way to manage micro-services (but this is an opinion of course :) ). Even when using a micro-services architecture, you can still have a single main Git repository (with independent micro-services inside it) and use a subtree split to create read-only repositories for each of your libraries. The main advantage is that it dramatically decreases the time needed to maintain multiple repositories (a single place for PR and issues) while keeping the flexibility and simplicity of micro-services. There are many options available to create subtree splits, don't hesitate to have a look.

For you issue, I understand our plans may not suit your needs. I am open to consider any proposal you may have for an offer that would match your needs as well as ours.

Thanks,
Best regards,

[jasny]

This is really a matter of opinion. Other CI tools like Travis and Scrutinizer limits the number of parallel (analyze) processes. So the basic plan can analyze one thing at a time. Op ma 27 aug. 2018 00:17 schreef Titouan Galopin <[email protected]>:

…

Thanks for your feedback. I still think having a single main repository is the best way to manage micro-services (but this is an opinion of course :) ). Even when using a micro-services architecture, you can still have a single main Git repository (with independent micro-services inside it) and use a subtree split to create read-only repositories for each of your libraries. The main advantage is that it dramatically decreases the time needed to maintain multiple repositories (a single place for PR and issues) while keeping the flexibility and simplicity of micro-services. There are many options available to create subtree splits, don't hesitate to have a look. For you issue, I understand our plans may not suit your needs. I am open to consider any proposal you may have for an offer that would match your needs as well as ours. Thanks, Best regards, — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGJ1SBIMV43dBfTGvj35P9f_9qB0xQKks5uUx5vgaJpZM4V9Q8e> .