User-flow built for you.
You can run Fireback as an standalone API provider for your mobile app, front-end project directly without any coding. Fireback has HTTP built in support, and makes all features available publicly, which you can expose that port on your webserver on port 80 and let the apps interact with it straight.
Some important key notes on webserver:
config.ymlread more about this configuration file on Yaml Configuration screen
ali@alis-MacBook-Pro ~ % fireback start [GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached. [GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production. - using env: export GIN_MODE=release - using code: gin.SetMode(gin.ReleaseMode) [GIN-debug] GET /socket.io/*any --> github.com/gin-gonic/gin.WrapH.func1 (4 handlers) [GIN-debug] POST /socket.io/*any --> github.com/gin-gonic/gin.WrapH.func1 (4 handlers) [GIN-debug] GET /books --> pixelplux.com/fireback/modules/books.HttpQueryBooks (4 handlers) ...
By default, all information will be stored in an SQLLite database. You can change this for MySQL. Since you have your webserver running on http://localhost:4500 now, let's go and create first user using postman.
Fireback comes with a basic user signup/signin/forgetpassword form called "SmartUI", we have written this for those who do not want to create that form by themselves and would rather use the dropin. This is not forced - if you want your own custom signup or signin form, you can build it around the "Public API" avaiable under "Passports" section.