* Adding the skeleton for Firestore integration * Adding the datasource & query editor forms Also adding the database changelog for the firestore plugin Commenting out the firestore.close() connection because that causes issues with multiple Firestore tenants running in the same JVM. * Adding the code for fetching the structure of collections from Firestore * Use single document path field for Firestore * Fix potential NPE when datasource destroy timeouts * Work in progress on collection level ops for Firestore * Get documents in a collection now works * Add collection level querying support * Mild refactoring * Fix NPE when some fields are missing * Hide clientJSON as a password field for Firestore * Make collection level querying reactive * Make reactive * Validate before connecting * Add tests for all supported methods in Firestore * Fix forms for Firestore with hidden fields * Hide limit and order by fields when not needed * Restore log entry deleted by mistake * Use S3 URL for Firestore/Firebase logo * Add comments detailing why some code is commented * Make parsing JSON reactive and fix subscribe calls * Fix reactive scheduler Co-authored-by: Arpit Mohan <arpit@appsmith.com> |
||
|---|---|---|
| .. | ||
| 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.