63fe27fae1
* Doing a deep copy during clone application instead of updating the original application which may have been causing a concurrency bug. * Ensuring that once the clone application flow is triggered, the flow completes eventually even if the client cancels the request before completion. * Cloned application would not be public. * Added parametrized Application constructor * Removed lombok all args constructor * Optimized import * Incorporated review comments : 1. Updated the constructor for creating the application 2. Added a test case to assert that if during cloning of an application the flow gets cancelled, the cloning would still complete and ensure that the application created is sane. |
||
|---|---|---|
| .. | ||
| appsmith-interfaces | ||
| appsmith-plugins | ||
| appsmith-server | ||
| envs | ||
| mongo-seed | ||
| scripts | ||
| .gitignore | ||
| build.sh | ||
| buildpack-run.sh | ||
| docker-compose.yml | ||
| Dockerfile | ||
| entrypoint.sh | ||
| pom.xml | ||
| Procfile | ||
| README.md | ||
| system.properties | ||
Appsmith Server
This is the server-side repo for the Appsmith framework.
How to build
$ ./build.sh <arguments>
For example:
$ ./build.sh -DskipTests
This script will perform the following steps:
- Compile the code
- Generate the jars for server & plugins
- Copy them into the
distdirectory
How to run
$ cd ./dist
$ java -jar -Dspring.profiles.active=$env server-1.0-SNAPSHOT.jar
How to test
In order to test the code, you can run the following command:
mvn -B clean package
Please make sure that you have a local Redis instance running for the test cases. During tests, the MongoDB is run in-memory. So you don't require to be running a local MongoDB instance.