Wappler is the first web creation tool I’ve used that does not allow the User to Create a Database Connection that can only be used by the Online Database Server.
Currently I must FTP to the Wappler folder when it is uploaded online.
Then I have to open the Wappler connection/s used during development & change the credentials Wappler allowed during development to the correct connection settings for Online Database access.
It would save time AND give one less critical step to keep in mind
if Wappler would not by default ASSUME that the Online Database URL or hostingprovider MUST MATCH the location or definition of the Database Hosting online.
I suppose this would be handy for a DB sqlite connection ?
When I select TARGET Wappler should also offer the option to create a Target defined as FTP Target does not resemble MySQL (MSSQL, etc) credentials.
OR, simply do not run this security check between a Connection & FTP targets.
Allow the User to create and save the Online Database Connections to be used later or immediately without giving any error as Invalid.
Give us perhaps a separate folder for Uploads – Same files as Development Application but with ONLINE Database valid credential string applied .
Then the FTP Target ONLINE will only upload Server Action connections that work ONLINE.
Last updated: