{"id":15377508,"url":"https://github.com/mislav/puppet-personal","last_synced_at":"2025-06-25T13:03:46.553Z","repository":{"id":4235404,"uuid":"5359167","full_name":"mislav/puppet-personal","owner":"mislav","description":"I'm learning Puppet. WIP","archived":false,"fork":false,"pushed_at":"2012-08-12T17:44:00.000Z","size":108,"stargazers_count":8,"open_issues_count":0,"forks_count":2,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-06-25T13:02:43.103Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Ruby","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/mislav.png","metadata":{"files":{"readme":"readme.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2012-08-09T18:01:03.000Z","updated_at":"2020-07-29T11:22:40.000Z","dependencies_parsed_at":"2022-09-22T01:11:12.439Z","dependency_job_id":null,"html_url":"https://github.com/mislav/puppet-personal","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/mislav/puppet-personal","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mislav%2Fpuppet-personal","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mislav%2Fpuppet-personal/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mislav%2Fpuppet-personal/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mislav%2Fpuppet-personal/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/mislav","download_url":"https://codeload.github.com/mislav/puppet-personal/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mislav%2Fpuppet-personal/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":261879271,"owners_count":23223736,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-01T14:12:03.501Z","updated_at":"2025-06-25T13:03:46.525Z","avatar_url":"https://github.com/mislav.png","language":"Ruby","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Mislav's Puppet experiments\n\nI'm no sysadmin expert but I've set up a personal server—usually\nDebian-flavored—countless times manually. Time to automatize this. I would want\nto be able to provision a single box quickly for personal use, but I want to do\nit via recipes that I or anyone else can easily re-apply against another box.\n\nI've brushed with Chef, but after getting disillusioned with its complexity,\nI've set out to try Puppet. Turns out, it's not any easier.\n\n![I have no idea what I'm doing](http://i0.kym-cdn.com/photos/images/newsfeed/000/234/142/196.jpg)\n\nBoth Chef and Puppet seem designed for uses much more sophisticated than\nprovisioning a single machine for personal use. I'm not sure if they're the\nright tool for the job for this.\n\n## What services I need\n\n* git\n* rbenv\n* postgresql, redis, mongo\n* elasticsearch\n* memcached\n* nginx vhosts + Passenger, running multiple Ruby apps\n* cron jobs for said apps\n* postfix + dovecot, for personal email\n\nMy target is CentOS 6.2 for now, but would like to support Ubuntu too so these\nrecipes get some wider reusability.\n\n## How I'm using puppet\n\nI have installed \"puppet\" gem on the remote server. I rsync the \"manifests\" and\n\"modules\" directories from my local machine up to the server and run \"puppet\napply\" there (see `apply.sh`).\n\nI'm using 2 puppet modules found on GitHub as git submodules: \"rbenv\" and \"postfix\".\n\n## Testing locally\n\nI test what I have right now locally using Vagrant.\n\n    $ vagrant up\n\nTo reprovision after making changes:\n\n    $ vagrant provision\n\n## The problems that I have\n\n1.  Using rbenv module doesn't work with `puppet apply`:\n\n        Could not autoload rbenvgem:\n          no such file to load -- puppet/provider/rbenvgem\n          at /root/puppet/modules/rbenv/manifests/gem.pp:22\n\n    AFAIK, the files in `{modulepath}/{module}/lib/pupppet/provider/` should be\n    autoloaded, but are not. **I've hacked this by setting**\n    `RUBYLIB=modules/rbenv/lib`.\n\n    Seems like [pluginsync won't work with\n    apply](https://github.com/puppetlabs/puppet/pull/427) until v3.0?\n\n## The questions that I have\n\n* Do I really have to manually manage RUBYLIB for plugins to work?\n* How should I organize my manifests into multiple files once my setup grows?\n* Is there a better way to run recipes on my remote box (currently rsync)\n  without resorting to master-client model?\n* How can I automate provisioning a new box that can't run puppet yet (no Ruby,\n  rubygems, or puppet gem installed); using old school shell scripts that I run\n  via ssh?\n* rbenv module currently manages bashrc; is there a way to hook into\n  `rbenv::install` for zshrc and avoid doing [zsh support\n  manually](https://github.com/mislav/puppet-personal/blob/55c3b61/manifests/centos62-64.pp#L10-17)?\n  Or should I contribute to upstream rbenv module?\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmislav%2Fpuppet-personal","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmislav%2Fpuppet-personal","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmislav%2Fpuppet-personal/lists"}