Skip to content
Go to file

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

poly-on-fire is a collection of proof-of-concept projects using Polymer and Firebase

Pete Carapetyan TL;DR? blog TL;DR? video:
pete jammazwanPhotoSmall about
A project for learning an aspect of developing a Polymer app, deployed on Firebase hosting.

The idea is to prove out an approach or component in the simplest project first, before combining it with other code in a real project.


What it does:

Unlike other poly-on-fire projects, autopm is not a client written in Polymer, but a back end server written in Java. It uses the Spring Boot and Apache Camel stacks, in addition to the Firebase Admin SDK.

Autopm runs on a server and listens for database changes to respond to. Things that it does on such a change are many, but include these functions:

  • Generating HTML pages and
  • Listening to file system changes and deploying html to a sibling firebase hosting project
  • Firing off a daily email run to selected recipients on selected topics
  • Misc admin such as responding to promotion requests

Here is what it looks like when it is running

youtube demo

This video walks you through the relationship between front and back ends and covers the primary functions of the back end codebase.

How I Install and Run It

from my bash shell:

mvn clean install -DskipTests
java -jar target/autopm.jar


You will need to have maven, java, and nvm installed, or else modify accordingly to use your current version of npm. Before you run the above maven and jar commands, you also need to have the appropriate firebase hosting project running in a sibling folder, for the generated html files to be able to deploy properly. Then, you run this script from the autopm folder, to initialize the sibling folder.



Nvm sets node version to latest stable except when functions are used in the project, when it uses a lower version to match requirements of functions API.

This is a polymer2 app modeled somewhat after polycast 61 by rob, which is a polymer1 demo.

This app arbitrarily uses a hide function to do it's demo.

There are better ways to do this hide, but since that isn't the core of the functionality, doesn't matter here.

This demo barely touches the redux api. When I did a real implementation after this demo app, I had to do a lot more experimentation, specifically within the reducer.


Back end processing for pullModel via Spring Boot, Camel, and firebase db listeners




No releases published


No packages published