fylein / fyle-sage-desktop-api Public

Notifications You must be signed in to change notification settings
Fork 0
Star 0

API to connect to Sage Desktop Products

0 stars 0 forks Branches Tags Activity

Notifications

Name		Name	Last commit message	Last commit date
Latest commit History 309 Commits
.github		.github
apps		apps
fyle-integrations-db-migrations @ b16d9f1		fyle-integrations-db-migrations @ b16d9f1
fyle_integrations_imports @ 0a8da84		fyle_integrations_imports @ 0a8da84
sage_desktop_api		sage_desktop_api
sage_desktop_sdk		sage_desktop_sdk
scripts		scripts
tests		tests
workers		workers
.coveragerc		.coveragerc
.dockerignore		.dockerignore
.flake8		.flake8
.gitignore		.gitignore
.gitmodules		.gitmodules
.pre-commit-config.yaml		.pre-commit-config.yaml
.pylintrc		.pylintrc
Dockerfile		Dockerfile
LICENSE		LICENSE
README.md		README.md
bandit.yaml		bandit.yaml
centralized_run.sh		centralized_run.sh
docker-compose-pipeline.yml		docker-compose-pipeline.yml
gunicorn_config.py		gunicorn_config.py
health_check.sh		health_check.sh
init.sql		init.sql
manage.py		manage.py
pytest.ini		pytest.ini
requirements.txt		requirements.txt
run.sh		run.sh
start_qcluster.sh		start_qcluster.sh

Repository files navigation

fyle-sage-desktop-api

API to connect to Sage Desktop Products

Adding a New View, Function, or Trigger:

Follow these steps to ensure your changes are applied correctly:
1. Make changes in the fyle-integrations-db-migrations repository.
2. Update the submodule in the Sage300 API:
```
git submodule init
git submodule update
```
3. Enter the Sage300 API container:
```
enter sage-desktop-api
```
4. Generate a migration file using the provided convenient command:
```
python3 manage.py create_sql_migration <file-path1>
```
  - Replace <file-path1> with the relative path to your SQL file from the fyle-integrations-db-migrations folder.
  - The migration will always be created in the internal app.
  Example:
```
python3 manage.py create_sql_migration fyle-integrations-db-migrations/sage300/functions/delete_workspace.sql
```
5. Review the newly generated migration file: Navigate to the apps/internal/migrations/ directory and ensure the migration file content is as expected.
6. Restart the Sage300 API service and apply the migration:
```
restart sage-desktop-api
logs sage-desktop-api
```
  Confirm in the logs that the migration has been applied successfully.