Deploying to Prod

Assuming you're using SQLite, deploying could not be easier. In fact, a lot of what sparked Prodigy in the first place was the frustration with deploying WordPress.

There are two pieces to put in place:

1. Code and static assets: Prodigy assumes you're managing your code deployment  process separately (i.e. using git).
2. /prodigy Database & Media: You have a /prodigy folder containing both your database and media files. Dragging that folder into place on the server replaces the dynamic content of the site.

Getting your deploy files

The easiest way to safely grab your files is to backup your prodigy instance and use that folder. That way you know you have a “checkpoint” for later, if needed.

Naming the database

At this moment, the database must be called prodigy.sqlite. Otherwise backups won't work. Soon, the database will be able to be named anything.

Relative URLs

Use relative URLs for all Prodigy pages and entries to enable seamlessly moving your site from server to server. This is a tremendous time saver.