This application can be deployed on Heroku or on a traditional server.

The following will provide three different types of deployments.

After installation, you will be able to connect with the nickname admin and the password password.

Deploying the application with Vagrant

Installation of VirtualBox and Vagrant

$ sudo apt-get install virtualbox
$ wget
$ sudo dpkg -i vagrant_1.8.5_x86_64.deb

Deployment of Newspipe

$ git clone
$ cd newspipe-vagrant/
$ vagrant up

Once the VM will be configured by Vagrant, go to the address

Deploying the application on Heroku

An instance of Newspipe is running here.

The geek way

$ git clone
$ cd newspipe
$ heroku create
Creating app... done, ⬢ secure-reef-83404 |
$ heroku addons:add heroku-postgresql:hobby-dev
$ heroku config:set HEROKU=1
$ heroku config:set PLATFORM_URL=
$ heroku config:set CDN_ADDRESS=
$ heroku buildpacks:add --index 1 heroku/python
$ heroku buildpacks:add --index 2
$ heroku buildpacks:add --index 3
$ git push heroku master
$ heroku run init
$ heroku ps:scale web=1

To enable account creation for users, you have to set some environment variables:

$ heroku config:set SELF_REGISTRATION=1
$ heroku config:set SECRET_KEY=<a secret token only you know in order to use sessions>
$ heroku config:set SECURITY_PASSWORD_SALT=<a secret to confirm user account>
$ heroku config:set TOKEN_VALIDITY_PERIOD=3600
$ heroku config:set NOTIFICATION_EMAIL=<notification-email>
$ heroku addons:create sendgrid:starter
$ heroku addons:docs sendgrid # read the documentation to get your API key
$ heroku config:set SENDGRID_API_KEY=<your-sendgrid-api-key>

SendGrid is used to send account confirmation links.

If you don’t want to open your platform just set SELF_REGISTRATION to 0. You will be still able to create accounts via the administration page.

The simple way

Alternatively, you can deploy your own copy of the app using this button:

You will be prompted to choose an email and a password for the administrator’s account. And some other optional environment variables, as previously presented.

Deploying the application on a traditional server

Configuration (database url, email, user agent, etc.) is done via the file src/conf/conf.cfg. Check this file before installing Newspipe.

$ git clone
$ cd newspipe/

If you want to use SQLite

$ ./ sqlite

If you want to use PostgreSQL

$ ./ postgres

Newspipe is now ready!

Configuration (database url, email, user agent, etc.) is done via the file src/conf/conf.cfg.

By default the one page app of Newspipe will be loaded from here. But you can also built it yourself. You’ll have to have Node.js installed:

$ npm install
$ npm run build

Then in the configuration file src/conf/conf.cfg set the variable cdn_address to the empty string.

Finally launch the Web server:

$ python src/
 * Running on
 * Restarting with reloader

Automatic updates and logging

You can fetch new articles with cron. For example if you want to check for updates every 30 minutes, add this line to your cron rules (crontab -e):

*/30 * * * * cd ~/.newspipe/ ; python src/ fetch_asyncio

If you want to see the logs of the crawler (when it is running on Heroku with the scheduler addon):

$ heroku logs --source app --dyno scheduler