Examples Templates Store Pricing Docs Turbo CSS Blog Introducing Turbo UI Named buckets Turbo CSS is Tailwind CSS on steroids Introducing Turbo CSS, the most advanced web-design language Calculate how much storage you use Better login system Collaboration settings Filesystem and Database are not cutting the problem space right What I'm working on 64bit File node IDs New how-to videos Creating buttons gets easier Introducing reusable components HTTPS by default Introducing the Boomla Theme CDN for faster pageloads Write your own website builder on top of Boomla On On composition Shared admin access A fresh config editor Building a multi-purpose theme A filesystem to replace your CMS New file link type: scope Mobile editing support Inline file wrapping changed Package sandboxing New PHP-like JavaScript engine [sjs-4e] Send emails to the website owner New JavaScript engine [sjs-4] A better editing experience New email service provider Glossary and other changes New panel changes Improved registration flow Boomla goes multiplayer Using local dev tools Why Boomla doesn't need Git File Panel Let's build a community Automatic updates Improved sjs-3 API New Frontend CSS modules Work offline with Boomla Faster page loads via caching Drag & drop supercharged Supporting CommonJS modules  Paranoid about loosing data IDE usability improvements Simple App install flow Meetups in Budapest Goodbye broken links Flow control from user space Customizing apps Contextmenu support for apps Deprecating the .Class file Hello Changelog Embedding 3rd party plugins Introducing Tools Installing apps just got amazing Public beta Host on our servers Simple deploy with push/pull Version Control for the Web 350M files on a 1TB disk 2 weeks in review
Control Panel

Using local dev tools

2018-07-21

I was asked by Gergő, a developer, if you can use your own editor with Boomla.

Short answer

Not now, yes in the past and future.

Long answer

We had support for using your local development tools in the past, and we will support it in the future. Because everyone seemed to be happy with our web based IDE, we decided to pull the plug on the local build to help us move faster.

Windows users: we have a built-in SFTP server for you, that maps the Boomla filesystem onto a POSIX compatible format. Currently it is only available in the local binary, which is not released. Let me know if you wanted to use it.

Mac and Linux users: We had FUSE integration in the past, which turned out to be buggy in some weird edge cases. I had to either fix or remove it. As nobody was using it, I removed it for now. It’s definitely coming back in the future. For the time being, I rather add features people care about. Let me know if you wanted to use it.

Unexpected

Interestingly, I was sure I wanted to work with my local tools, and only built the IDE for others. Over time, I gradually stopped using my local dev tools, to my biggest surprize. Using the web IDE is just faster. For example, file drag-and-drop is way simpler in the web based IDE, as Boomla files are stored in order, not alphabetically.

So, if you are in my old shoes and want to use your own dev tools, you may want to give the web based IDE a try regardless. And if you have ideas on how to improve it, go ahead, fork it and send me a pull request.


Cheers,

you can follow me on Twitter