Quickstart
Start here to build a basic Pushkin site and experiment.
Last updated
Was this helpful?
Start here to build a basic Pushkin site and experiment.
Last updated
Was this helpful?
If you haven't installed pushkin-cli and its dependencies, start here first.
Make sure Docker is running by running the command docker info; if it isn't, you can run dockerd or sudo dockerd to start it.
Open a terminal window. Create an empty directory (e.g., pushkin_quickstart) and enter this directory using the following commands:
(For more on basic terminal commands, you can check out this blog post.)
Install your first pushkin site the in the directory you just created:
You will be asked to select a site template to use. Choose basic, then choose the recommended version.
(See example output for this command here.)
This sets up a skeleton website in the current folder and a development database. Once the command finishes, you should have a directory tree like this:
The files in the pushkin folder won’t need to be edited at all except those in the front-end folder.
Open pushkin.yaml in your project root directory. It should look something like:
You can ignore most of these (or all, if you want to keep the defaults). But probably you should change:
whoAmI: This is the name of your website that will be displayed to users
shortName: An abbreviated name of your website
hashtags: These are hashtags used for social media
email: An email where notifications, etc., will be sent to.
The one you should definitely change is salt. This is used to encrypt private information. Type in any alphanumeric text here -- for instance:
To create a new experiment from the boilerplate template Pushkin provides, run
Choose a basic experiment. When prompted, name your experiment vocab and choose the recommended version. Choose 'no' when asked if you want to import a jsPsych experiment. Repeat the process to add basic experiments called mind and whichenglish as well.
(See example output for this command here.)
This will create a new folder in the experiments directory like this:
Each experiment has its own folder. Within this experiment-specific folder, there is also configuration file (config.yaml), which allows you to define a human-readable full name for the experiment (e.g., Which English? for whichenglish), specify a database to use, and make other customizations.
Keeping all the files for an experiment within the same root folder is convenient for development, but not for actually deploying the website. To redistribute the experiment files to the right places, run:
(See example output for this command here.)
Coming soon!
Now, let’s look at your website! Make sure Docker is running by running the command docker info; if it is not, you can run dockerd or sudo dockerd to start it. Next, run:
(See example output for this command here.)
Now browse to http://localhost to see the stub website.
If you are using an AWS EC2 instance, navigate to the IPv4 Public IP address of your instance instead of http://localhost. This can be found in the AWS EC2 console. Note: You will not be able to locally test a default site if you are using an AWS EC2 instance. The authentication software used in the default site template requires the site to be accessed from localhost. In order to locally test a site on an AWS EC2 instance, it must have a "basic" site template.
When you are done looking at your website, stop it by running:
If you don’t do that, the web server will keep running in Docker until you quit Docker or restart. When the command has finished running, it should output done.
Every time you update code or add an experiment, you’ll need to run pushkin prep again:
By default, the Pushkin creates a database called test_db where your data is stored. (This is explained in further detail here.) In order to view your database and easily see your data, you should install a Postgres Manager such as SQLPro for Postgres, which costs $7.99/month after the free trial ends. Free and open-source managers are also available (e.g., pgAdmin). Or, if you become very comfortable connecting to postgres through the command line (not documented in this tutorial), then you may not need a Postgres manager.
This tutorial will assume that you've downloaded and installed pgAdmin. Windows, macOS, and Ubuntu users can all download pgAdmin from their official download page. Ubuntu users can also install it from the command line using these instructions.
When you start pgAdmin, it will take a moment to load and then will appear as a new tab in your web browser. When you install it the first time, it will ask you to set a master password. This can be whatever you'd like, but make sure you keep it in a secure place.
Under the Quick Links, click Add New Server. (Make sure you have run pushkin start; and that your site is running in localhost or at your IPv4 Public IP address.) Then follow these steps:
You can set the name of the server to anything, for example Pushkin Testing.
Then move to the Connection tab and set Host name/address to localhost (or your IPv4 Public IP address).
Set the password to the default password, example, which you can find in pushkin.yaml.
Click Save and your Pushkin Testing server should appear in the left sidebar.
To view your data tables, navigate to the left sidebar:
Click to expand your Pushkin Testing server.
Select test_db under Databases.
Select Schemas, which will also open its subitem public.
Under public, choose Tables.
By default, you should have 5 tables: knex_migrations, knex_migrations_lock, pushkin_userMeta, pushkin_userResults, and pushkin_users. You should also have one table for each experiment; if you've followed this tutorial, you should also have mind_stimulusResponses, vocab_stimulusResponses, and which_english_stimulusResponses.
To view a given table, right-click on it, hover over View/Edit Data, and click on All Rows, which will then appear in a new pgAdmin tab.
For more information on how to use pgAdmin, you can read their documentation here.
The great thing about Docker is that it saves your work. (Read up on Docker to see what I mean.) The bad thing is that it saves your work. Simply editing your code locally may not change what Docker thinks the code is. If you are updating something but it’s not showing up in your website or if you are getting error messages from Docker … ideally, you should read up on Docker. However, as a fail-safe, run pushkin kill to delete all your Pushkin-specific code in Docker. Then just run pushkin prep again. This will take a while but should address any Docker-specific problems. If you really need a fresh Docker install, run pushkin armageddon, which will completely clean Docker.
To get the latest news and updates on Pushkin, sign up for our newsletter here.
