williamscs / hydraprint Goto Github PK

In reference to Issue #6.

Some preliminary ideas include the obvious:
/jobs/:job
/printers/:printer

But I don't know the full extent of what we'll need. I'll keep this issue open while we figure out what routes we will end up needing.

I was thinking we should implement something simple. Just a header, body, footer sort of architecture.

The header would allow us to navigate between the following:
Printers
Jobs

hmmm.... I really think that's it.
Anyway, V1, lets just have a boring header and footer, and basic body that is dynamically populated without refreshing the page.

Put under website layout since this will be needed for viewing job and printer statuses.

Prerequisite is that user has installed Print Manager
Two use cases:
Print Manager installed on Desktop/Laptop
Print Manager installed on dedicated linux machine (i.e. raspberry pi)

In either case, HyraPrint is a client that could be deployed on the machine or in the cloud as a job manager.
V1 proposal: a Herokuapp with oauth login (gmail, twitter, or facebook?). Will default to using localhost IP address initially. User can setup HydraPrint to point at an array of additional IP addresses including localhost, any specific IP address, even bonjour style IP address. Herokuapp will store user's registered Print Manager IP address(s). Common use case could be users subscribing their machine using ngrock