This is my first bash script! What do you think? You plug in your droplet ip, your domain and your gitlab info and in 5 minutes your web app is live at https://yourdomain, and all future commits to main are automatically deployed. Included templates for new django, flask and fastApi projects!

• ezinnit

  16 15 10.0 Shell

  ezinnit initializes your gitlab repository and your server. Your app will be live and commits to main will automatically deploy.

• install

  9 2,053 6.7 Shell

  📥 Homebrew (un)installer

  

Beyond what I've already said, I would refer you to look at how, e.g. Homebrew install.sh (and other repos in that project) handle a comparable setup. You can see a lot of what I have been flagging in there: tests, functions, comments, not making permanent changes outside remit, etc.

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• Chocolatey

  393 9,849 8.4 C#

  Chocolatey - the package manager for Windows

  

Let's tale a real world example- I use Homebrew and I have used chocolatey where I have had to use a Windows machine. Both of these use shell scripts for initial setup and both of them have a 'stub' one-liner that you can paste into your system shell and calls remote scripts. I feel that I can trust the reputation of each of these projects and that if I wished I could inspect the full script myself. Not everyone would and there are techniques in each case for confining these tools. I don't know you or the reputation of your project, or the licenses for these third party package install scripts. I would suggest that you concentrate on making it as easy as possible for your user to: - install/use your thing - inspect what your thing does

• HomeBrew

  1,281 39,303 10.0 Ruby

  🍺 The missing package manager for macOS (or Linux)

  

Let's tale a real world example- I use Homebrew and I have used chocolatey where I have had to use a Windows machine. Both of these use shell scripts for initial setup and both of them have a 'stub' one-liner that you can paste into your system shell and calls remote scripts. I feel that I can trust the reputation of each of these projects and that if I wished I could inspect the full script myself. Not everyone would and there are techniques in each case for confining these tools. I don't know you or the reputation of your project, or the licenses for these third party package install scripts. I would suggest that you concentrate on making it as easy as possible for your user to: - install/use your thing - inspect what your thing does

Suggest a related project