You can follow the process below to get a wq-powered application up and running.
If you are using wq.app and wq.db together, you can use the
wq start command provided by the wq Django template. You will need a WGSI-capable webserver like Apache, and a database to host the application. wq.db is generally used with PostgreSQL and PostGIS, but any Django-supported database will work. You can also use wq.app by itself and replace wq.db with your own backend solution.
pip3 install wq wq start [PROJECTNAME]
Note: wq is optimized for Python 3. Python 2.7 is still supported for the time being, but should be considered deprecated. If you are using Python 2.7, be sure to remove the "3" from the db/manage.py file created by wq start.
Detailed installation instructions are available for each of the following operating systems:
wq does not come with a canned data model by default. This makes it extremely flexible to adapt to a variety of project workflows. However, it does require a bit more work to get set up initially as you must define your data model yourself. After installing wq and starting a project via
wq start, the next steps are usually to:
rest.py(see the db/exampleapp folder created by wq start). Add [appname] to your
INSTALLED_APPSsetting in db/[projectname]/settings.py
models.py. In the simplest case, each model will have the same fields as the forms you're planning on creating. In more complex applications, you may want to leverage one of the Model patterns provided by wq.db. The distinction between these approaches is discussed in this article.
./manage.py dbshell, psql, or pgAdmin to confirm that the tables were created.
rest.pyfile that registers each model class with the wq.db router. You can open a browser and visit your website's /config.json and /modelnames.json to confirm that the model(s) are registered.
Once your data model is defined and your REST API is running, you can start implementing a user interface to create, retrieve, update, and potentially delete records in your database. To do this, you'll mostly just need to create Mustache templates for each model's "list", "detail" and "edit" views, that populate HTML screens with data from the REST API. In order to provide the maximum flexibility for your project, wq doesn't provide much of a canned user interface, though the example templates provided by the
wq start command should get you started. Don't be afraid to learn a little HTML!
The Species Tracker source code is useful as an example of the changes needed to turn the output of
wq start into a fully functional application.