Cross-platform installer tool idea for Drogon

[Kushan20070126]

I started working on a small CLI tool to simplify Drogon setup across Linux, macOS, and Windows.

One command setup for Drogon
Reduce manual install steps
Improve onboarding for new users

basic commands:

drogon-installer install
drogon-installer install --only-deps
drogon-installer install --skip-build
drogon-installer create myapp

Features:

OS detection (Linux, macOS, Windows)
Auto install dependencies
Clone Drogon repo
Build and install
Create new project using drogon_ctl
Optional verbose logging

First version focuses on Linux support , macOS and Windows support added after
i used Python 3 CLI tool, Platform scripts (bash, PowerShell)
Does this direction fit the project ecosystem?
Would a tool like this be useful in official docs or tooling?
Open to feedback before finalizing structure.

repo : https://github.com/Kushan20070126/drogon-installer.git

[albaropereyra22]

This is cool, I’ve worked on something similar but have separate programs for different operating systems.  I use bash so I can install everything with one line of code.  That’s what I recommend you do.  Have bash install the dependencies, test the environment to your script (python3), and clone the repo. I hope this is integrated.Sent from my iPhoneOn Apr 22, 2026, at 3:21 AM, Kushan Randika Herath ***@***.***> wrote: I started working on a small CLI tool to simplify Drogon setup across Linux, macOS, and Windows. One command setup for Drogon Reduce manual install steps Improve onboarding for new users basic commands: drogon-installer install drogon-installer install --only-deps drogon-installer install --skip-build drogon-installer create myapp Features: OS detection (Linux, macOS, Windows) Auto install dependencies Clone Drogon repo Build and install Create new project using drogon_ctl Optional verbose logging First version focuses on Linux support , macOS and Windows support added after i used Python 3 CLI tool, Platform scripts (bash, PowerShell) Does this direction fit the project ecosystem? Would a tool like this be useful in official docs or tooling? Open to feedback before finalizing structure. repo : https://github.com/Kushan20070126/drogon-installer.git —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Kushan20070126]

Hi,

Thanks for the feedback. This helps.

I’m planning to shape the tool a bit more around what you mentioned. For Linux, I’ll add a small bootstrap Bash script so users can get everything set up with a single command. That script will handle checking for things like python3, git, and cmake, install anything missing, and then hand things over to the CLI.

On the main side, I’ll keep Python as the core of the tool. It makes handling OS detection, commands, and logging much easier across platforms, so Bash and PowerShell will just handle the system-level work.

I also want to make the install experience smoother. I’m aiming for a simple one-liner using curl for quick setup, plus a pip install option for people who prefer that route.

I’ll tighten up environment checks too, so the tool fails early with clear messages or installs what’s missing where possible. And I’ll keep the commands straightforward and predictable, sticking with things like install, --only-deps, --skip-build, and create.

Overall goal is to make setup easy for new users while keeping things clean and maintainable for the Drogon ecosystem.

I’ll push these updates soon. Happy to hear any more thoughts if you have them.

Thanks again,
Kushan

[albaropereyra22]

Cool, this is my current one liner that installs my entire development environment on a Mac. /bin/sh -c "$(curl -fsSL https://raw.githubusercontent.com/albaropereyra22/MacScripts/HEAD/installEverything.sh)”

…

On Apr 23, 2026, at 7:57 AM, Kushan Randika Herath ***@***.***> wrote: Hi, Thanks for the feedback. This helps. I’m planning to shape the tool a bit more around what you mentioned. For Linux, I’ll add a small bootstrap Bash script so users can get everything set up with a single command. That script will handle checking for things like python3, git, and cmake, install anything missing, and then hand things over to the CLI. On the main side, I’ll keep Python as the core of the tool. It makes handling OS detection, commands, and logging much easier across platforms, so Bash and PowerShell will just handle the system-level work. I also want to make the install experience smoother. I’m aiming for a simple one-liner using curl for quick setup, plus a pip install option for people who prefer that route. I’ll tighten up environment checks too, so the tool fails early with clear messages or installs what’s missing where possible. And I’ll keep the commands straightforward and predictable, sticking with things like install, --only-deps, --skip-build, and create. Overall goal is to make setup easy for new users while keeping things clean and maintainable for the Drogon ecosystem. I’ll push these updates soon. Happy to hear any more thoughts if you have them. Thanks again, Kushan — Reply to this email directly, view it on GitHub <#2501?email_source=notifications&email_token=BBZFRV5G62YPWRYWGD3RJTL4XIVNDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWHA3DCOBTUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-16686183>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBZFRV7M44MOZFMXKME6P5T4XIVNDAVCNFSM6AAAAACYCEI6I6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNRYGYYTQMY>. You are receiving this because you commented.

[Kushan20070126]

Did you find a way for Windows? Bash scripts don't work on Windows, right?

[albaropereyra22]

No, they don’t you need to call a batch scripts on Windows, there might be a way for one script to run the batch script once we determine it is windows. The power shell keeps getting closer and closer to bash.

…

On Apr 24, 2026, at 9:21 PM, Kushan Randika Herath ***@***.***> wrote: Can you find a way for Windows? Bash scripts don't work on Windows, right? — Reply to this email directly, view it on GitHub <#2501 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBZFRV5MRST7DXPAI2MFV3D4XQ4NDAVCNFSM6AAAAACYCEI6I6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNZQHA4TANY>. You are receiving this because you commented.