[Docs] Document a way to install Appsmith manually without the install.sh script
See original GitHub issueThere have been requests to provide a document with an initial template of docker-compose.yml
file and then list out what needs to be done to get an Appsmith instance up. This will be a useful alternative when folks don’t want to (or are unable to) run the install.sh
script to get started.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:7
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Installing Appsmith On K8s Using Helm Charts - YouTube
Hey folks . In our community call this week, will have Shri from our engineering team talk about k8s and how to install...
Read more >How to Deploy the Appsmith Low Code Platform With Docker
A First Deployment · Setting Up Appsmith · Using Supervisor · Using Docker Compose · Writing Your Own Compose File · Updating Your...
Read more >Free Developer Stuff
Open source diary and journal software for Linux, Windows and Mac. ... edit, preview and share themes and theme components without installing Discourse!...
Read more >Connection String URI Format — MongoDB Manual
This document describes the URI formats for defining connections between applications and MongoDB instances in the official MongoDB Drivers.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I don’t like to run shell scripts directly from repositories either. I understand, that this project is mainly for “no code” guys with not much experience, but for those, who have already a production environment, this installation method is not ideal.
Having a docker-compose.yml and some .env files would be better for the most existing environments. The installation script also collects the IP address as “installation id” and (currently) 23 events over a web-hook in the install.sh script. I could not find the place in the documentation where this is described and the script also does not seem to ask for consent. I can understand, that the developers want to know, what happens and where their application is installed, but this behavior should be at least declared in the documentation.
@AndrewBedscastle’s workaround brings more effort to launch the app, but seems the only good way to get the “clean” compose files. I tried to copy everything from the scripts in the deploy folder (deploy/template/) but it requires some customization, which I do not have time for.
Hey @brasilikum, yep, we do have a fat container now, but its currently a little lacking in documentation. I’m running it through a few more rounds of testing before publishing it to the wider audience. Coming super soon 🤞