We were using PATCH, because that was semantically more correct for what we are doing here. But since PUT is used everywhere else in the project, changing this to PUT for consistency. |
||
|---|---|---|
| .. | ||
| .run | ||
| 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 repository 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.