The best way to achieve this is by using the Data Mesh feature as you already mentioned. You can refer to this guide - https://blog.dreamfactory.com/easier-data-marts-with-dreamfactory-data-mesh/
Also, you could also add certain conditions in the API call itself. Look at the documentation here - https://guide.dreamfactory.com/docs/chapter03.html#generating-a-mysql-backed-api.
Doing the above will result in only call one API endpoint to achieve the desired results. Let me know if it helps
This error happen for a wide variety of reasons. Normally, this error can be due to a temporary overloading or maintenance being performed on the server and it is resolved after a period of time or once another thread has been released by web-server application. In most cases this could happen (assuming there are no faults in your app) if there are long running tasks and as a result the request queue is backed up.The subsequent points serve as a possible fix, aimed toward resolving the 503 Service Unavailable Error.
We have configured the HTTP services to call the our microservice apis. When we get the response of an API, it comes as a single object {} data is there. But when it’s empty object, it comes as an array ; which conflicts with the data type that we’re maintaining.
null is a legal value (and reserved word) in JSON, but some environments do not have a “NULL” object (as opposed to a NULL value) and hence cannot accurately represent the JSON null . So they will sometimes represent it as an empty array. Whether null is a legal value in that particular element of that particular API is entirely up to the API designer.
I have created 2 HTTP service for a single micro service, both in different environment and using different dream factory version respectively:-
So when calling from the the 1st HTTP service, everything works as expected but from the latter it does not.
Unfortunately the open source is discontinued… no one to support… death of DF…
Hi folks,
I am experiencing this bug and I am wondering if anyone else has seen it.
I have two database services to two different Oracle databases. I created a role with GET access to _table/* in one database and _table/SCHEMA.MY_TABLE/* in the other, where SCHEMA.MY_TABLE is a specific table in another schema. I give this role to the api_docs app for a regular user.
When that user logs in and looks at the API docs, there are no endpoints listed for the service with the one table, it just shows a message: “No operations defined in spec!”. The other database lists the appropriate three endpoints. If I change the single table in the role to _table/* like the other database, the api docs look correct.
Has anyone experienced this bug?
Thanks in advance for any help.
Hi, I am wondering if DF supports invalidation of a session in the web application after a period of inactivity. It doesn’t seem so because even though you can set a TTL on the JWT token, each click in the web app refreshes the token even if it has expired. So the only way you force logout in the web app is if the entire session is beyond the DF_JWT_REFRESH_TTL, regardless of activity.
My installation: DF Gold version 4.2.1 on a local Bitnami Docker installation.
Thanks in advance for any help.
Hi @lakshay
Can you provide a stack trace or a screenshot of the error that you are encountering?
DF_ALLOW_FOREVER_SESSIONS=false
Changing the above parameter in your .env file will allow you to have sessions that will remain active unless you logout. As you already know, you can set this parameter and use it in conjunction with DF_JWT_REFRESH_TTL.
Hope it helps
@abhishek.pandey thanks for the reply but it does not really answer my question. I want the web session to act like many other web sites where the user gets logged out after a period of inactivity. Do you understand that concept? It means the user is idle and has not clicked anything. From what I can tell, any click in the web admin console refreshes the token, so the user will always stay logged in until DF_JWT_REFRESH_TTL minutes. I did not change DF_ALLOW_FOREVER_SESSIONS which I assume leaves it false, but the documentation does not say what the default is.
I want the period of inactivity to be one hour so I want to set DF_JWT_TTL=60 but it doesn’t matter because it will refresh until DF_JWT_REFRESH_TTL which I have set to 480 or 8 hours.
Hi @abhishek.pandey
getting 400 Bad Request.
Also can you tell me how to get the logs.
400 Bad Request could result from a bad request URL. I cannot be sure without looking at the HTTP request. I am sure that it is not due to you using bitnami-dreamfactory-4-0-1-0-r02-linux-debian-9-x86-64.
Logs can be found under Files -> Logs -> dreamfactory.log
I created a HTTP remote service through the open source DreamFactory. I encountered a major problem when testing the application.
When I directly send GET and POST requests to the service (not through DF) the context type received is the correct one : application/json
However, when I send the same request via the DF, the context type received is application/x-www-form-urlencoded.
It’s causing problems with my application since it expects application/json type of request. How can I fix that?
Hi @dx4
It is because the keys and values are encoded in key-value tuples separated by '&' , with a '=' between the key and the value when you send it via DreamFactory.
In your GET/POST requests, you can add an additional header field called ‘content-type’ and set the value to application/json. That should work.
KEY - content-type
VALUE - application/json
Not sure what I can post to narrow down this bug in the DreamFactory framework
I have found that if I rename the table to something else the flipped boolean problem goes away. Same table, different name. “screening” is the table name DreamFactory API has the trouble with.
Hi,
I managed to install a DF instance with MySQL as a backend. The instance is running fine, i am able to create new apps and services.
However, when I tried to install the second DF instance (for HA) with same MySQL as backend, after executing php artisan df:setup i got a message as Your instance is already setup.
I had gone through the whitepaper scaling-the-dreamfactory-services-platform for Horizontal scaling. I understood that DF is just a application running on a web server, which can talk to a common backend database. That’s it
I didn’t found any other resources guiding on how to run multiple instances of DF behind a load balancer.
Any help is appreciated.
Thanks
Please
Hi folks,
My DF instance is up and running, but ctlscript.sh and the linux manager won’t recognize the status of Apache, or let me restart it. Any ideas how I can regain control of Apache?
I need to replicate the effect of SQL “REPLACE INTO” query with the REST verbs.
REPLACE INTO does what INSERT INTO does, except it will overwrite an existing matching record.
We’ve got GET, POST, PUT, PATCH, DELETE. I have tried testing POST, PUT, and PATCH in API Docs but none have achieved the “insert with overwrite” effect so far. POST fails on existing record, PUT and PATCH fail if there is nothing to overwrite.
How do I achieve that insert with overwrite effect?
