General purpose backend framework.
Features:
Check out the Documentation for more documentation.
The module supports several databases and includes ImageMagick interface so in order for such interfaces to be compiled the software must be installed on the system before installing the backendjs. Not everything is required, if not available the interface will be skipped.
The list of optional packages that the backendjs may use if available, resolving packages is done by pkg-config:
Installing on CentOS:
yum -y install libpng-devel openjpeg-devel libjpeg-turbo-devel jasper postgresql-devel mysql-devel
Installing on Mac OS X using macports:
port install libpng jpeg tiff jasper mysql56 postgresql93
To install the module with all optional dependencies if they are available in the system
Note: if for example ImageMagick is not istalled it will be skipped, same goes to all database drivers(PostgreSQL, MySQL) and nanomsg.
npm install backendjs
To force internal nanomsg and ImageMagick to be compiled the following command must be used:
npm install backendjs --backend_deps_force
This may take some time because of compiling required dependencies like ImageMagick, nanomsg and LevelDB. They are not required in all applications but still part of the core of the system to be available once needed.
Run default backend without any custom extensions, by default it will use embedded Sqlite database and listen on port 8000
rc.backend run-backend
Documentation is always available when the backend Web server is running at http://localhost:8000/doc.html
Go to http://localhost:8000/api.html for the Web console to test API requests. For this example let's create couple of accounts, type and execute the following URLs in the Web console
/account/add?name=test1&secret=test1&login=test1@test.com
/account/add?name=test2&secret=test2&login=test2@test.com
Now login with any of the accounts above, click on Login at the top-right corner and enter email and secret in the login popup dialog.
If no error message appeared after the login, try to get your current account details:
/account/get
To see all public fields for all accounts just execute
/account/select
Shutdown the backend by pressing Ctrl-C
To make your own custom Web app, create a new directory (somewhere else) to store your project and run the following command from that directory:
rc.backend init-app
The app.js file is created in your project directory with 2 additional API endpoints /test/add and /test/[0-9] to show the simplest way
of adding new tables and API commands.
The app.sh script is created for convenience, it specifies common arguments and can be customized as needed
Run new application now, it will start the Web server on port 8000:
./app.sh
Go to http://localhost:8000/api.html and issue /test/add?id=1&name=1 and then /test/1 commands in the console to see it in action
Change in any of the source files will make the server restart automatically letting you focus on the source code and not server management, this mode is only enabled by default in development mode, check app.sh for parameters before running it in te production.
The backend support multiple databases and provides the same db layer for access. Common operations are supported and all other specific usage can be achieved by using SQL directly or other query language supported by any particular database. The database operations supported in the unified way provide simple actions like get, put, update, delete, select, the query method provides generic access to the databe driver and executes given query directly.
Before the tables can be queried the schema must be defined and created, the backend db layer provides simple functions to do it:
first the table needs to be described, this is achieved by creating a Javascript object with properties describing each column, multiple tables can be described at the same time, for example lets define album table and make sure it exists when we run our application:
api.describeTables({
album: {
id: { primary: 1 }, // Primary key for an album
name: { pub: 1 }, // Album name, public column
mtime: { type: "bigint" }, // Modification timestamp
},
photo: {
album_id: { primary: 1 }, // Combined primary key
id: { primary: 1 }, // consiting of album and photo id
name: { pub: 1, index: 1 }, // Photo name or description, public column with the index for faster search
mtime: { type: "bigint" }
}
});
the system will automatically create the album and photos tables, this definition must remain in the app source code and be called on every app startup. This allows 1) to see the db schema while working with the app and 2) easily maintain it by adding new columns if necessary, all new columns will be detected and the database tables updated accordingly. And it is all Javascript, no need to learn one more language or syntax to maintain database tables.
Each database may restrict how the schema is defined and used, the db layer does not provide an artificial layer hidning all specific, it just provides the same API and syntax, for example, DynamoDB tables must have only hash primary key or combined hash and range key, so when creating table to be used with DynamoDB, only one or two columns can be marked with primary property while for SQL databases the composite primary key can conisist more than 2 columns.
The accounts API manages accounts and authentication, it provides basic user account features with common fields like email, name, address.
/account/get
Returns information about current account or other accounts, all account columns are returned for the current account and only public columns returned for other accounts. This ensures that no private fields ever be exposed to other API clients. This call also can used to login into the service or verifying if the given login and secret are valid, there is no special login API call because each call must be signed and all calls are stateless and independent.
Parameters:
Note: When retrieving current account, all properties will be present including the location, for other accounts only the properties marked as pub in the
bk_account table will be returned.
Response:
{ "id": "57d07a4e28fc4f33bdca9f6c8e04d6c3",
"alias": "Test User",
"name": "Real Name",
"mtime": 1391824028,
"latitude": 34,
"longitude": -118,
"geohash": "9qh1",
"login": "testuser",
}
/account/add
Add new account, all parameters are the columns from the bk_account table, required columns are: name, secret, login.
By default, this URL is in the list of allowed paths that do not need authentication, this means that anybody can add an account. For the real application this may not be a good choice so the simplest way to disable it to add api-disallow-path=^/account/add$ to the config file or specify in the command line. More complex ways to perform registration will require adding pre and.or post callbacks to handle account registration for example with invitation codes....
In the table bk_auth, the column type is used to distinguish between account roles, by default only account with type admin can
add other accounts with this type specified, this column can also be used in account permissions implementations. Because it is in the bk_auth table,
all columns of this table are avaailable as req.account object after the successful authentication where req is Express request object used in the middleware
parameters.
Note: secret and login can be anything, the backend does not require any specific formats so one simple trick which is done by the backend Web client is to scramble login/secret using HMAC-SHA1 and keep them in the local storage, this way the real login and secret is never exposed but the login popup will still asking for real name, see backend.js in the web/js folder for more details.
Example:
/account/add?name=test&login=test@test.com&secret=test123&gender=f&phone=1234567
/account/select
Return list of accounts by the given condition, calls db.select for bk_account table. Parameters are the column values to be matched and
all parameters starting with underscore are control parameters that goes into options of the db.select call with underscore removed. This will work for SQL
databases only because DynamoDB or Cassandra will not search by non primary keys. In the DynamoDB case this will run ScanTable action which will be very expensive for
large tables.
Example:
/account/search?email=test&_ops=email,begins_with
/account/search?name=test&_keys=name
Response:
{ "data": [{
"id": "57d07a4e28fc4f33bdca9f6c8e04d6c3",
"alias": "Test User1",
"name": "User1",
"mtime": 1391824028,
"login": "test1",
},
{
"id": "57d07a4e2824fc43bd669f6c8e04d6c3",
"alias": "Test User2",
"name": "User2",
"mtime": 1391824028,
"login": "test2",
}],
"next_token": ""
}
/account/del
Delete current account, after this call no more requests will be authenticated with the current credentials
/account/update
Update current account with new values, the parameters are columns of the table bk_account, only columns with non empty values will be updated.
Example:
/account/update?name=New%2BName&alias=Hidden%2BName&gender=m
/account/put/secret
Change account secret for the current account, no columns except the secret will be updated and expected.
Parameters:
Example:
/account/put/secret?secret=blahblahblah
/account/subcribe
Subscribe to account events delivered via HTTP Long Poll, a client makes the connection and waits for events to come, whenever
somebody updates the account's counter or send a message or creates a connection to this account the event about it will be sent to this HTTP
connection and delivered as JSON object. This is not a persistent queue so if not listening, all events will just be ignored, only events published
since the connect will be delivered. To specify what kind of events needs to be delivered, match query partameters can be specified which is a
RegExp of the whole event body string.
Note: On the server side there is a config parameter subscribeInterval which defines how often to deliver notifications, by default it is 5 seconds which means
only every 5 seconds new events will be delivered to the Web client, if more than one event happened, they all accumulate and will be sent as a JSON list.
Example:
/account/subscribe
/account/subscribe?match=connection/add.*type:*like
Response:
[ { "path": "/message/add", "mtime:" 1234566566, "sender": "23545666787" },
{ "path": "/counter/incr", "mtime:" 1234566566, "data": { "like": 1, "invite": 1 } },
{ "path" : "/connection/add", "mtime": 1223345545, "type": "like", "id": "123456789" } ]
/account/select/icon
Return a list of available account icons, icons that have been uploaded previously with /account/put/icon calls. The url property is an URL to retrieve this particular icon.
Parameters:
Example:
/account/select/icon?id=12345
Response:
[ { id: '12345', type: '1', url: '/account/get/icon?id=12345&type=1' },
{ id: '12345', type: '2', url: '/account/get/icon?id=12345&type=2' } ]
/account/get/icon
Return an account icon, the icon is returned in the body as binary BLOB, if no icon with specified type exists, i.e. never been uploaded then 404 is returned.
Parameters:
Example:
/account/get/icon?type=2
/account/put/icon
Upload an account icon, once uploaded, the next /account/get call will return propertis in the format iconN wheer N is any of the
type query parameters specified here, for example if we uploaded an icon with type 5, then /account/get will return property icon5 with the URL
to retrieve this icon.
By default all icons uploaded only accessible for the account which uploaded them.
Parameters:
application/json and data should be sent with POST requestExample:
/account/put/icon?type=1&icon=iVBORw0KGgoAAAANSUhEUgAAAAcAAAAJCAYAAAD+WDajAAAABGdBTUEAALGPC/xhBQAAAAlwSFlzAAAOwgAADs....
/account/del/icon
Delete account icon
Parameters:
Example:
/account/icon/del?type=1
This endpoint can server any icon uploaded to the server for any account, it is supposed to be a non-secure method, i.e. no authentication will be performed and no signagture
will be needed once it is confgiured which prefix can be public using api-allow or api-allow-path config parameters.
The format of the endpoint is:
/image/prefix/id/type
Example:
# Configure accounts icons to be public in the etc/config
api-allow-path=/image/account/
# Or pass in the command line
./app.sh -api-allow-path /image/account/
# Make requests
/image/account/12345/0
/image/account/12345/1
#Return icons for account 12345 for types 0 and 1
The icons API provides ability for an account to store icons of different types. Each account keeps its own icons separate form other
accounts, within the account icons can be separated by prefix which is just a name assigned to the icons set, for example to keep messages
icons separate from albums, or use prefix for each separate album. Within the prefix icons can be assigned with unique id which can be any string.
/icon/get/prefix
/icon/get/prefix/type
Return icon for the current account in the given prefix, icons are kept on the local disk in the directory
configured by -api-images-dir parameter(default is images/ in the backend directory). Current account id is used to keep icons
separate from other accounts. If type is used to specify any unique icon created with such type which can be any string.
/icon/put/prefix
/icon/put/prefix/type
Upload new icon for the given account in the folder prefix, if type is specified it creates an icons for this type to separate
multiple icons for the same prefix. type can be any string consisting from alpha and digits characters.
The following parameters can be used:
/account/put/icon for the format and usage/icon/del/prefix
/icon/del/prefix/type
Delete the default icon for the current account in the folder prefix or by type
/icon/select/prefix
/icon/select/prefix/type
Return list of available icons for the given prefix adn type, all icons starting with prefix/type will be returned,
the url property will provide full URL to retrieve the icon contents
Example:
/icon/select/album/me
Response:
[ { id: 'b3dcfd1e63394e769658973f0deaa81a', type: 'me1', icon: '/icon/get/album/me1' },
{ id: 'b3dcfd1e63394e769658973f0deaa81a', type: 'me2', icon: '/icon/get/album/me2' } ]
The connections API maintains two tables bk_connection and bk_reference for links between accounts of any type. bk_connection table maintains my
links, i.e. when i make explicit connection to other account, and bk_reference table is automatically updated with reference for that other account that i made
a connection with it. No direct operations on bk_reference is allowed.
/connection/add
/connection/put
Create or replace a connection between two accounts, required parameters are:
id - id of account to connect totype - type of connection, like,dislike,....This call automatically creates a record in the bk_reference table which is reversed connection for easy access to information like ''who is connected to me'' and auto-increment like0, like1 counters for both accounts in the bk_counter table.
Also, this call updates the counters in the bk_counter table for my account which match the connection type, for example if the type of
connection is 'invite' and the bk_counter table contain 2 columns invite0 and invite1, then both counters will be increased.
Example:
/connection/add?id=12345&type=invite&state=sent
/connection/update
Update other properties of the existing connection, for connections that may take more than i step or if a connection has other data associated with it beside
the type of the connection.
Example:
/connection/update?id=12345&type=invite&state=accepted
/connection/del
Delete existing connection, id and type must be specified, mass-deletion is not supported only one conection by one.
Example:
/connection/del?type=invite&id=12345
/connection/get
Receive all my connections of the given type, i.e. connection(s) i made, if id is given only one record for the specified connection will be returned
Example:
/connection/get?type=invite - return all accounts who i invited
/connection/get?type=invite&id=12345
Response:
{ "data": [ { "id": "12345",
"type": "invite",
"status": "",
"mtime": "12334312543"
}],
"next_token": ""
}
/reference/get
Receive all references that connected with my account, i.e. connections made by somebody else with me, works the same way as for connection query call
Example:
/reference/get?type=invite - return all accounts who invited me
Response:
{ "data": [ { "id": "57d07a4e28fc4f33bdca9f6c8e04d6c3",
"type": "invite",
"status": "",
"mtime": "12334312543"
}],
"next_token": ""
}
/connection/recent
Return all connections made since the given time, parameter mtime defiens the point in time which connections have been made after this time, this is for
fast retrieval only recent connections without pulling a long list every time to see who connected. This requires for the client to maintain the timestamp of the last
request and update it with the mtime from the most recent connection.
Example:
/connection/recent?mtime=1392185596577
Response:
{ "data": [ { "id": "12345",
"type": "invite",
"status": "",
"mtime": "12334312543"
},
{ "id": "45678",
"type": "like",
"status": "",
"mtime": "12334312543"
}],
"next_token": ""
}
The location API maintains a table bk_location with geolocation coordinates for accounts and allows searching it by distance.
/location/put
Store currenct location for current account, latitude and longitude parameters must be given, this call will update the bk_accout table as well with
these coordinates
Example:
/location/put?latitude=-188.23232&longitude=23.4545454
/location/get
Return matched accounts within the distance(radius) specified by distance= parameter in kilometers and current position specified by latitude/longitude paraemeters. This
call returns results in chunks and requires navigation through all pages to receive all matched records. Records returned will start with the closest to the current
point. If there are more matched records than specified by the _count, the next_token property is set with the token to be used in the subsequent call,
it must be passed as is as _token= parameter with all original query parameters.
By default only locations with account ids will be returned, specifying _details=1 will return public account columns like name as well.
Note: The current account will not be present in the results even if it is within the range, to know my own location use /account/get call.
Example:
/location/get?distance=10&latitude=-118.23434&longitude=23.45665656&_count=25
/location/get?distance=10&latitude=-118.23434&longitude=23.45665656&_count=25&_token=FGTHTRHRTHRTHTTR.....
Response:
{ "data": [ { "id": "12345",
"distance": 5,
"latitude": -118.123,
"longitude": 23.45
"mtime": "12334312543"
},
{ "id": "45678",
"distance": 5,
"latitude": -118.133,
"longitude": 23.5
"mtime": "12334312543"
}],
"next_token": ""
}
The messaging API allows sending and recieving messages between accounts, it supports text and images. The typical usage of this API is to
poll the counter record using /counter/get from time to time and check for msg_count and msg_read counters, once msg_count is greater than msg_read this means
there is a new message arrived. Then call /message/get to retrieve all or only new messages arrived after some point in time and store the mtime
from the last messages received so the next time we will use this time to get only new messages.
/message/image
Return the image data for the given message, the required parameters are:
/message/get reply results for every message/message/get
Receive messages, the parameter mtime defines which messages to get, if omitted all messages will be returned. By mtime it is possible to
specify that only messages received since that time to return, it must be in milliseconds since midnight GMT on January 1, 1970, this is what
Date.now() return in Javascript. The images are not returned, only link to the image in icon property of reach record,
the actual image data must be retrieved separately.
NOTE: The mtime is when the backend server received the message, if client and the server clocks are off this may return wrong data or not return anything at all,
also because the arrival order of the messages cannot be guaranteed, sending fast multiple messages may be received in different order by the backend and this will
result in mtimes that do not correspond to actual times when the message has been sent.
Example:
/message/get
/message/get?mtime=123475658690
Response:
{ "data": [ { "sender": "12345",
"msg": "Hi, how r u?",
"mtime": "12334312543"
},
{ "sender": "45678",
"msg": "check this out!",
"icon": "/message/image?sender=45678&mtime=12334312543",
"mtime": "12334312543"
}],
"next_token": ""
}
/message/get/unread - read all unread messages, i.e. the meesages that never been issues /message/read call. This call does not require any query
parameters, it will return all unread messages from all senders.
/message/add
Send a message to an account, the following parametrrs must be specified:
id - account id of the receivermsg - text of the message, can be empty if icon property existsicon - icon of the message, it can be base64 encoded image in the query or JSON string if the whole message is posted as JSON or
can be a multipart file upload if submitted via browser, can be omitted if msg/connection/get?type=invite&id=12345 property exists.After successful post the message counters of the destination account will be updated: msg_count will be increased automatically
Example:
/message/add?id=12345&msg=Hello
/message/add?id=12345&msg=this%2Bis%2Bthe%2Bpic&icon=KHFHTDDKH7676758JFGHFDRDEDET....TGJNK%2D
/message/read
Mark a message as read, this will update account counter msg_read automatically. The required query parameters are sender and mtime.
Example:
/message/read?sender=12345&mtime=12366676434
/message/del
Delete the message by sender and mtime which must be passed as query parameters.
Example:
/message/del?sender=12345&mtime=124345656567676
The counters API maintains realtime counters for every account records, the counters record may contain many different counter columns for different purposes and is always cached with whatever cache service is used, by default it is cached by the Web server process on every machine. Web worker processes ask the master Web server process for the cached records thus only one copy of the cache per machine even in the case of multiple CPU cores.
/counter/get
Return counter record for current account with all available columns of if id is given return public columns for given account, it works with bk_counter table
which by default defines some common columns:
/counter/put
Replace my counters record, all values if not specified will be set to 0
/counter/incr
Increase one or more counter fields, each column can provide a numeric value and it will be added to the existing value, negative values will be substracted.
if id parameter is specified, only public columns will be increased for other account.
Example:
/counter/incr?msg_read=5&
/counter/incr?id=12345&ping=1
The history API maintains one table for all application specific logging records. All operations deal with current account only.
/history/add
Add a record to the bk_history table for current account, timestamp is added automatically, all other fields are optional but by default
this table contains only 2 columns: type and data for genetic logging, it can to be extended to support any other application logic if needed.
/history/get
Return history record for current account, if mtime is not specified all records from the beginning will be returned, use _count and _start parameters to paginate through
all available records or specify mtime= with the timestamp in milliseconds to start with particular time.
The data API is a generic way to access any table in the database with common operations, as oppose to the any specific APIs above this API only deals with one table and one record without maintaining any other features like auto counters, cache...
Because it exposes the whole database to anybody who has a login it is a good idea to disable this endpoint in the production or provide access callback that verifies who can access it.
To disable this endpoint completely in the config: api-disable=data
To allow admins to access it only:
api.registerAuthCheck('GET', '/data', function(req, status, cb) { if (req.account.type != "admin") return cb({ status: 401, message: 'access denied' }; cb(status)); });
/data/stats
Database pool statistics and other diagnostics
Individual sub-objects:
Response:
{
"toobusy": 0,
"pool": {
"process": {
"meter": {
"mean": 0.001194894762493158,
"count": 65,
"currentRate": 0.001194894762493158,
"1MinuteRate": 2.413646785930864e-158,
"5MinuteRate": 1.2021442332952544e-33,
"15MinuteRate": 7.127940837162242e-13
},
"histogram": {
"min": 1,
"max": 4,
"sum": 99,
"variance": 0.4096153846153847,
"mean": 1.523076923076923,
"stddev": 0.6400120191179106,
"count": 65,
"median": 1,
"p75": 2,
"p95": 2.6999999999999957,
"p99": 4,
"p999": 4
}
},
"queue": {
"min": 1,
"max": 1,
"sum": 65,
"variance": 0,
"mean": 1,
"stddev": 0,
"count": 65,
"median": 1,
"p75": 1,
"p95": 1,
"p99": 1,
"p999": 1
},
"count": 0,
"rate": {
"mean": 0.0011948946746301802,
"count": 65,
"currentRate": 0.0011948946746301802,
"1MinuteRate": 2.413646785930864e-158,
"5MinuteRate": 1.2021442332952544e-33,
"15MinuteRate": 7.127940837162242e-13
},
"response": {
"meter": {
"mean": 0.0011948947405274121,
"count": 65,
"currentRate": 0.0011948947405274121,
"1MinuteRate": 2.413646785930864e-158,
"5MinuteRate": 1.2021442332952544e-33,
"15MinuteRate": 7.127940837162242e-13
},
"histogram": {
"min": 0,
"max": 2,
"sum": 65,
"variance": 0.12500000000000003,
"mean": 1,
"stddev": 0.3535533905932738,
"count": 65,
"median": 1,
"p75": 1,
"p95": 2,
"p99": 2,
"p999": 2
}
},
"misses": 3,
"hits": 50
},
"api": {
"rss": {
"min": 77926400,
"max": 145408000,
"sum": 23414882304,
"variance": 234721528417225.16,
"mean": 128653199.47252747,
"stddev": 15320624.282881724,
"count": 182,
"median": 124903424,
"p75": 144999424,
"p95": 145408000,
"p99": 145408000,
"p999": 145408000
},
"heap": {
"min": 14755896,
"max": 31551408,
"sum": 4174830592,
"variance": 19213862445722.168,
"mean": 22938629.626373626,
"stddev": 4383362.002586846,
"count": 182,
"median": 22453472,
"p75": 26436622,
"p95": 30530277.599999998,
"p99": 31331225.599999998,
"p999": 31551408
},
"loadavg": {
"min": 0,
"max": 0.14208984375,
"sum": 8.33349609375,
"variance": 0.0013957310299007465,
"mean": 0.04578844007554945,
"stddev": 0.03735948380131538,
"count": 182,
"median": 0.043701171875,
"p75": 0.0806884765625,
"p95": 0.103857421875,
"p99": 0.13803710937499994,
"p999": 0.14208984375
},
"freemem": {
"min": 1731198976,
"max": 1815724032,
"sum": 319208222720,
"variance": 335910913486664.44,
"mean": 1753891333.6263735,
"stddev": 18327872.584854588,
"count": 182,
"median": 1757151232,
"p75": 1763340288,
"p95": 1785729638.4,
"p99": 1798348267.5199997,
"p999": 1815724032
},
"rate": {
"mean": 0.005091340673514894,
"count": 277,
"currentRate": 0.005091340673514894,
"1MinuteRate": 0.014712537947741827,
"5MinuteRate": 0.003251074139103506,
"15MinuteRate": 0.0011131541240945431
},
"response": {
"meter": {
"mean": 0.005072961780912493,
"count": 276,
"currentRate": 0.005072961780912493,
"1MinuteRate": 0.014712537947741827,
"5MinuteRate": 0.003251074139103506,
"15MinuteRate": 0.0011131541240946244
},
"histogram": {
"min": 1,
"max": 11847,
"sum": 13614,
"variance": 508182.2787351782,
"mean": 49.32608695652174,
"stddev": 712.8690473959282,
"count": 276,
"median": 2,
"p75": 5.75,
"p95": 27.149999999999977,
"p99": 122.99000000000024,
"p999": 11847
}
},
"queue": {
"min": 1,
"max": 2,
"sum": 286,
"variance": 0.03154920734578558,
"mean": 1.032490974729242,
"stddev": 0.17762096538918368,
"count": 277,
"median": 1,
"p75": 1,
"p95": 1,
"p99": 2,
"p999": 2
},
"count": 1
}
}
/data/columns
/data/columns/TABLE
Return columns for all tables or the specific TABLE
/data/keys/TABLE
Return primary keys for the given TABLE
/data/(select|search|list|get|add|put|update|del|incr|replace)/TABLE
Perform database operation on the given TABLE, all options for the db functiobns are passed as query parametrrs prepended with underscore,
regular parameters are the table columns.
Example:
/data/get/bk_account?id=12345
/data/put/bk_counter?id=12345&like0=1
/data/select/bk_account?name=john&_ops=name,gt&_select=name,alias,email
When the backend server starts and no -home argument passed in the command line the backend makes its home environment in the ~/.backend directory.
The backend directory structure is the following:
etc - configuration directory, all config files are there
etc/config - config parameters, same as specified in the command line but without leading -, each config parameter per line:
Example:
debug=1
db-pool=dynamodb
db-dynamodb-pool=http://localhost:9000
db-pgsql-pool=postgresql://postgres@127.0.0.1/backend
To specify other config file: rc.backend run-backend -config-file file
etc/crontab - jobs to be run with intervals, local or remote, JSON file with a list of cron jobs objects:
Example:
Create file in ~/.backend/etc/crontab with the following contents:
[ { "type": "local", "cron": "0 1 1 * * 1,3", "job": { "api.cleanSessions": { "interval": 3600000 } } } ]
Define the funtion that the cron will call with the options specified, callback must be called at the end, create this app.js file
var backend = require("backendjs");
backend.api.cleanSessions = function(options, callback) {
backend.db.del("session", { mtime: options.interval + Date.now() }, { ops: "le", keys: [ "mtime" ] }, callback);
}
backend.server.start()
Start the scheduler and the web server at once
rc.backend run-backend -master -web
etc/proxy - HTTP proxy config file, from http-proxy (https://github.com/nodejitsu/node-http-proxy)
Example:
Create file ~/.backend/etc/proxy with the following contents:
{ "target" : { "host": "localhost", "port": 8001 } }
Start the proxy
rc.backend -proxy
Now all requests will be sent to localhost:8001
etc/profile - shell script loaded by the rc.backend utility to customize env variables
images - all images to be served by the API server, every subfolder represent naming space with lots of subfolders for imagesvar - database files created by the servertmp - temporary filesweb - Web pages served by the static Express middlewareThe backend includes internal C++ module which provide some useful functions available in the Javascript. The module is exposed as "backend" submodule, to see all functions for example run the below:
var backend = require('backendjs');
console.log(backend.backend)
List of available functions:
rungc() - run V8 garbage collector on demand
setsegv() - install SEGV signal handler to show crash backtrace
setbacktrace() - install special V8-aware backtrace handler
backtrace() - show V8 backtrace from current position
heapSnapshot(file) - dump current memory heap snapshot into a file
splitArray(str) - split a string into an array separated by commas, supports double quotes
logging([level]) - set or return logging level, this is internal C++ logging facility
loggingChannel(channelname) - redirect logging into stdout or stderr, this is internal C++ logging
countWordsInit()
countWords()
countAllWords()
resizeImage(source, options, callback) - resize image using ImageMagick,
resizeImageSync(name,width,height,format,filter,quality,outfile) - resize an image synchronically
snappyCompress(str) - compress a string
snappyUncompress(str) - decompress a string
geoDistance(lat1, lon1, lat2, lon2) - return distance between 2 coordinates in km
geoBoundingBox(lat, lon, distance) - return bounding box geohash for given point around distance
geoHashEncode(lat, lon, len) - return geohash for given coordinate, len defines number of bytesin geohash
geoHashDecode(hash) - return coordinates for given geohash
geoHashAdjacent()
geoHashGrid()
geoHashRow()
cacheSave()
cacheSet()
cacheGet()
cacheDel()
cacheKeys()
cacheClear()
cacheNames()
cacheSize()
cacheEach()
cacheForEach()
cacheForEachNext()
cacheBegin()
cacheNext()
lruInit(max) - init LRU cache with max number of keys, this is in-memory cache which evicts older keys
lruStats() - return statistics about the LRU cache
lruSize() - return size of the current LRU cache
lruCount() - number of keys in the LRU cache
lruSet(name, val) - set/replace value by name
lruGet(name) - return value by name
lruIncr(name, val) - increase value by given number, non existent items assumed to be 0
lruDel(name) - delete by name
lruKeys() - return all cache key names
lruClear() - clear LRU cache
lruServer()
syslogInit(name, priority, facility)
syslogSend(level, text)
syslogClose()
listStatements() - list all active Sqlite statements
NNSocket() - create a new nanomsg socket object
Publish/subscribe functionality allows clients to receive notifications without constantly polling for new events. A client can be anything but
the backend provides some partially implemented subscription notifications for Web clients using the Long Poll. The Account API call /account/subscribe
can use any pub/sub mode.
This is default setup of the backend when all API requests except /account/add must provide valid signature and all HTML, Javascript, CSS and image files
are available to everyone. This mode assumes that Web developmnt will be based on 'single-page' design when only data is requested from the Web server and all
rendering is done using Javascript. This is how the api.html develpers console is implemented, using JQuery-UI and Knockout.js.
To see current default config parameters run any of the following commands:
rc.backend run-backend -help | grep api-allow
node -e 'require("backendjs").core.showHelp()'
To disable open registration in this mode just add config parameter api-disallow-path=^/account/add$ or if developing an application add this in the initMiddleware
api.initMiddleware = function(callback) {
this.allow.splice(this.allow.indexOf('^/account/add$'), 1);
}
This is a mode when the whole Web site is secure by default, even access to the HTML files must be authenticated. In this mode the pages must defined 'Backend.session = true' during the initialization on every html page, it will enable Web sessions for the site and then no need to sign every API reauest.
The typical client Javascript verification for the html page may look like this, it will redirect to login page if needed, this assumes the default path '/public' still allowed without the signature:
<link href="/styles/jquery-ui.css" rel="stylesheet" type="text/css" />
<script src="/js/jquery.js" type="text/javascript"></script>
<script src="/js/jquery-ui.js" type="text/javascript"></script>
<script src="/js/knockout.js" type="text/javascript"></script>
<script src="/js/crypto.js" type="text/javascript"></script>
<script src="js/backend.js" type="text/javascript"></script>
<script src="js/backend-jquery-ui.js" type="text/javascript"></script>
<script>
$(function () {
Backend.session = true;
Backend.scramble = true;
ko.applyBindings(Backend);
Backend.login(function(err, data) {
if (err) window.location='/public/index.html';
});
});
</script>
On the backend side in your application app.js it needs more secure settings defined i.e. no html except /public will be accessible and
in case of error will be redirected to the login page by the server. Note, in the login page Backend.session must be set to true for all
html pages to work after login without singing every API request.
First we disable all allowed paths to the html and registration:
api.initMiddleware = function(callback) {
self.allow.splice(self.allow.indexOf('^/$'), 1);
self.allow.splice(self.allow.indexOf('\\.html$'), 1);
self.allow.splice(self.allow.indexOf('^/account/add$'), 1);
}
Second we define auth callback in the app and redirect to login if the reauest has no valid signature, we check all html pages, all allowed html pages from the /public will never end up in this callback because it is called after the signature check but allowed pages are served before that:
api.registerAuthCheck('', /^\/$|\.html$/, function(req, status, callback) {
if (status.status != 200) {
status.status = 302;
status.url = '/public/index.html';
}
callback(status);
});
The purpose of the rc.backend shell script is to act as a helper tool in configuring and managing the backend environment and as well to be used in operations on production systems. It is not required for the backend operations and provided as a convenience tool which is used in the backend development and can be useful for others running or testing the backend.
Running without arguments will bring help screen with description of all available commands.
The tool is multi-command utility where the first argument is the command to be executed with optional additional arguments if needed. On startup the rc.backend tries to load and source the following config files:
/etc/backendrc
/usr/local/etc/backendrc
~/.backend/etc/profile
Any of the following config files can redefine any environmnt variable thus pointing to the correct backend environment directory or customize the running environment, these should be regular shell scripts using bash syntax.
Most common used commands are:
Here is the typical example how to setup new AWS server:
ec2-user home directory of the new instanceec2-usersudo ./rc.backend setup-server/etc/backendrc like BACKEND_ARGS, BACKEND_NAME, BACKEND_ROOT env variables,
if not set the defaults will be used.backend user now using the AWS keypair private keyThe first thing when deploying the backnd into production is to change API port, by default is is 800, but we would want port 80 so regardless how the environment is setup it is ultimatley 2 way to specify the port for HTTP server to use:
config file
The config file is always located in the etc/ folder in the backend home directory, how the home is specified depends on the system but basically it can be
defined via command line arguments as -home or via environment variables when using rc.backend. See rc.backend documentation but on AWS instances created with rc.backend
setup-server command, for non-standard home use /etc/backendrc profile, specify BACKEND_HOME=/home/backend there and the rest will be takedn care of
command line arguments
When running node scripts which use the backend, just specify -home command line argument with the directory where yor backend should be and the backend will use it
Example:
node test_backend.js -home $HOME
All requests to the API server must be signed with account login/secret pair.
The resulting signature is sent as HTTP header bk-signature: string
For JSON content type, the method must be POST and no query parameters specified, instead everything should be inside the JSON object which is placed in the body of the request. For additional safety, SHA1 checksum of the JSON paylod can be calculated and passed in the signature, this is the only way to ensure the body is not modified when not using query parameters.
See web/js/backend.js for function Backend.sign or function core.signRequest in the core.js for the Javascript implementation.
git clone https://github.com/vseryakov/backendjs.git or git clone git@github.com:vseryakov/backendjs.git
cd backend
to initialize environment for the backend development it needs to set permissions for $BACKEND_PREFIX (default is /opt/local) to the current user, this is required to support global NPM modules.
If $BACKEND_PREFIX needs to be changed, create ~/.backend/etc/profile file, for example:
mkdir -p ~/.backend/etc
echo "BACKEND_PREFIX=$HOME/local" > ~/.backend/etc/profile
Important: Add NODE_PATH=$BACKEND_PREFIX/lib/node_modules to your environment in .profile or .bash_profile so node can find global modules, replace $BACKEND_PREFIX with the actual path unless this variable is also set in the .profile
to install node.js in $BACKEND_PREFIX/bin if not installed already run command:
./rc.backend build-node
once node.js is installed, make sure all required modules are installed, this is required because we did not install the backend via npm with all dependencies, make sure this runs in the core backend directory:
./rc.backend npm-deps
now run the init command to prepare the environment, rc.backend will source .backendrc, this is required when the backend is used from the sources only
./rc.backend init-backend
to compile the binary module and all required dependencies just type make
for DB drivers and ImageMagick to work propely it needs some dependencies to be installed:
port install libpng jpeg librsvg tiff jasper lcms2 mysql56 postgresql93
to see the actual compiler setting during compile the following helps:
make V=1
to compile with internal nanomsg and ImageMagick use:
make force V=1
to run local server on port 8000 run command:
./rc.backend run-backend
to start the backend in command line mode, the backend environment is prepared and initialized including all database pools. This command line access allows you to test and run all functions from all modules of the backend without running full server similar to node.js REPL functionality. All modules are accessible from the command line.
$ ./rc.backend run-shell
> core.version
'2013.10.20.0'
> logger.setDebug(2)
Vlad Seryakov
Check out the Documentation for more documentation.
FAQs
A platform for building backends
The npm package backendjs receives a total of 23 weekly downloads. As such, backendjs popularity was classified as not popular.
We found that backendjs demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.
Security News
Research
Socket's threat research team has detected five malicious npm packages targeting Roblox developers, deploying malware to steal credentials and personal data.