puppet-stringer installs and deploys an instance of
Stringer, "A [work-in-progress]
self-hosted, anti-social RSS reader.".
Stringer needs several things to get going:
- dependent packages (not yet implemented, want to test one-by-one)
- separate user and group (done using resources)
- the Stringer source code (done using vcsrepo)
- an rbenv installation with ruby 2.0.0 (using alup/rbenv)
- necessary environment variables in bashrc (done using exec resource)
- cron job to update feeds (done using cron resource)
foreman startcommand to get going (done, but timing is iffy)
This is a very rough first draft, which needs significant re-factoring, tests, specs, etc., and more importantly, to actually be working. It is based off these instructions. Relevant issue.
My current hurdle is the use of the rbenv::bundle resource to
automatically install the dependencies in the Gemfile. This seemed
straightforward, but it has a requirement on an undocument
rbenv::client resource, which I'm not sure how to set up, or what it
is used for; relevant
upstream issue.
I need to go through the recommended package requirements, and determine which packages on which platforms actually need to be installed.
The PostgreSQL database setup I actually think should not be handled in this module. It certainly could be via the postgresql module, but it is probably better to let users manage said module outside of this one. Personally, I manage this in hiera, loosely following the roles/profiles pattern.
Copyright 2014 Andrew Schwartzmeyer. Provided under the included MIT Licesne.