Open pyrographics opened 2 years ago
Hey John,
Thanks for asking. Can you tell us how you use it in your workflow, specifically? If you'd feel more comfortable discussing it out of the public eye, you're welcome to sent an email to help [at] modx [dot] com and we'll chat there.
Specifically, we move sites to and from MODXCloud for development and publishing. We use the package manager to install the vapor packages in sites not on MODXCloud.
@craigflood I can bring this up to the Cloud team to discuss your use cases of Vapor and to see if this is something we can solve. The vast majority of developers who use MODX Cloud are building in Cloud and deploying between Clouds rather than local to Cloud workflows. We don't want MODX Cloud to be less useful to long-time users and MODX friends. Leave this with me and I'll get back to folks early in the new year.
For a little context, we originally developed Vapor as an easy way for people to bring their sites hosted at other hosting providers into Cloud. These days, for most new customers we migrate their sites into Cloud for free. Internally we use rysnc where possible because they were faster and more reliable—especially as it relates to certain content types and that doesn't get hung up on some custom Plugins and Snippets.
@jaygilmore thanks for the update. I have since removed my earlier comment. I'd be more than happy to understand in detail how other developers are building in cloud. I would much prefer to work this way.
@craigflood However you're using MODX Cloud is entirely valid and just because most customers and developers are doing it one way, may not be right for you but I'd be happy to discuss your workflow 1 on 1 and find out what we can do better, including potentially making Vapor work with Revo 3.
@pyrographics I haven't forgotten about you. We'll put this on topics for January 2023.
@jaygilmore đź‘Ť
Are you planning MODX 3 support for this extra? I use it a lot.