caf1d3f95c
Defining custom domain as `https://example.com/` is invalid. It should be just the domain, just `example.com`. But turns out a lot of our users have the incorrect configuration, and our previous stack of NGINX+Certbot was able to ignore this and serve without HTTPS. This PR brings that behaviour back. ## Test performed Have Appsmith running on an EC2 instance, and a domain `correct.com` with an A-record pointed to this EC2 instance. In the instance, we run Appsmith with `APPSMITH_CUSTOM_DOMAIN` set to `wrong.com`. Caddy will obviously fail to provision the cert, and so we expect it to accept connections on just HTTP. So hitting `curl -i http://correct.com` produced a 200 with the HTML response, and not a 308 with a redirect. Before the changes from this PR, the same curl command produced a 308 with a redirect to `https://correct.com`, which fails with a certificate error. Next up, we run Appsmith with `APPSMITH_CUSTOM_DOMAIN` set to `correct.com`. Caddy will succeed in provisioning a cert, and so we expect HTTP URLs to be redirected to HTTPS. So hitting `curl -i http://correct.com` produces a 308 redirect to `http://correct.com` which then works fine, since Caddy now has the cert for the domain. |
||
|---|---|---|
| .github | ||
| app | ||
| contributions | ||
| deploy | ||
| scripts | ||
| static | ||
| utils/observability | ||
| .deepsource.toml | ||
| .editorconfig | ||
| .env.example | ||
| .gitignore | ||
| .imgbotconfig | ||
| .nojekyll | ||
| app.json | ||
| appsmith_events.md | ||
| appsmith_templates.md | ||
| ci-debug.sh | ||
| CODE_OF_CONDUCT.md | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| depot.json | ||
| Dockerfile | ||
| heroku.yml | ||
| IssuesReport.md | ||
| LICENSE | ||
| README.md | ||
| SECURITY.md | ||
Organizations build internal applications such as dashboards, database GUIs, admin panels, approval apps, customer support dashboards, and more to help their teams perform day-to-day operations. Appsmith is an open-source tool that enables the rapid development of these internal apps. Read more on our website.
Installation
There are two ways to start using Appsmith:
- Signup on Appsmith Cloud.
- Install Appsmith on your machine. See the installation guides below.
| Installation Methods | Documentation |
|---|---|
 |
Docker (Recommended) |
 |
Kubernetes |
 |
AWS AMI |
For other deployment options, see the Installation Guides documentation.
Development
To build and run Appsmith in your local dev environment, see Setup for local development.
Learning Resources
Need Help?
Contributing
We ❤️ our contributors. We're committed to fostering an open, welcoming, and safe environment in the community.
📕 We expect everyone participating in the community to abide by our Code of Conduct. Please read and follow it.
🤝 If you'd like to contribute, start by reading our Contribution Guide.
👾 Explore some good first issues.
Let's build great software together.
Top Contributors
License
Appsmith is licensed under the terms of Apache License 2.0.