![]() I do not use Wappler deployment because I haven’t found a way to make it work for me as I use CI/CD elements. The targets stuff is very confusing for old and new users. Just not sure if the target settings should stay there and be extended (those are tabs as well), or should we make a whole new targets management/configuration settings panel. So what will be your ideal organizations of target settings and deployment workflow? So as you can see we have tons of target specific settings that are now pretty much scattered all over the place. Consolidate the other target specific settings like database connections, server connect globals - with the global target settings (preferred) or offer a target dropdown to choose where you edit them on (less preferred). ![]() Maybe make a whole new panel for targets only where you can manage each target and their options Improve project options - targets editing.Add more options to the deploy action, like choose target and and maybe directly git commit description tag version, like with the publishing to Heroku now.Remove the target choice drop down below - you are always working on local development target.To achieve this ultimate goal, we want to rework the workflow and improve the UI’s to make this more clear. The flow we want to follow is to always work on a local development target and only when you are done, choose a target to deploy to and hit the deploy to complete a full controlled deployment. However working on other targets than the local development target, has always caused confusion and errors. As we are getting some great discussions and ideas about the upcoming features of Wappler 4, there is another topic I wanted to gather as much feedback as possible and that is the deployment and target management.Ĭurrently we define in the Project options, various targets that you want to work on and deploy to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |