summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2012-11-03A POSIX shell is enough to run export-keyTails developers
2012-11-03Make export-key fail if any command failsTails developers
2012-11-03Create temp file in the same directory as the file it'll replace to get an ↵Tails developers
atomic update in export-key
2012-11-03Fail-close if multiple-keys are present by quoting KEY in export-keyTails developers
2012-11-03Always remove tempfile if something wrong happen in export-keyTails developers
2012-11-03Use uppercase for global shell variablesTails developers
2012-11-03Properly quote @basedir paths in export-keyTails developers
2012-11-03Use Debian style indentation in export-keyTails developers
2012-11-03Test for 'something' instead of 'not nothing' in export-keyTails developers
2012-11-03Use new-style shell expansion in export-keyTails developers
2012-11-03Add support for status in initscriptTails developers
2012-11-03Add a default value for $USER in initscriptTails developers
Relying on the external shell environment can lead to issue hard to understand. We explicitly set USER to root by default, and let admins override it in the default file.
2012-11-03Adjust whitespaces in initscriptsTails developers
2012-11-03Remove useless boilerplate from skeleton initscriptTails developers
2012-11-03Improve descriptions in initscriptTails developers
2012-11-03Fix boot dependencies in initscriptTails developers
inoticoming lies in /usr/bin so it needs $remote_fs and not $local_fs.
2012-11-03Have inoticoming perform an initial search of the directoryTails developers
If inoticoming is not started while new packages are added to the incoming directory, those packages would not have been processed straight away. So, instead of waiting for a subsequent package upload, let's just have inoticoming perform an initial run on startup.
2012-11-03Ensure that 'ensure' is the first attributeTails developers
See Style Guide: <http://docs.puppetlabs.com/guides/style_guide.html#attribute-ordering>
2012-11-03Group related exec and file resourcesTails developers
2012-11-03Define each file and exec resources separatelyTails developers
See Style Guide: <http://docs.puppetlabs.com/guides/style_guide.html#compression>
2012-11-03Use recommanded style for file modesTails developers
See Style Guide: <http://docs.puppetlabs.com/guides/style_guide.html#file-modes>
2012-11-03Have Puppet check mandatory class parameter is passed, rather than doing it ↵intrigeri
by hand.
2012-10-25Remove useless $server from file sourcesTails developers
2012-10-25Add warnings for file that are managed by PuppetTails developers
2012-10-25Processing the incoming queue requires the directory to be thereTails developers
2012-10-25Reduce duplication by using defaults for File resourcesTails developers
2012-10-25Convert the reprepro class to parametrized formatTails developers
We remove the deprecated dynamic lookup for variables and now have them as class parameters. The reprepro::cron and reprepro::inoticoming classes have been integrated in the reprepro class as two boolean arguments. As these are not mutually exclusive, it is cleaner that way. We add a test manifest for the reprepro class along the way.
2012-10-25Don't setup init script manuallyTails developers
There is no need to exec `update-rc.d` manually, the service definition will take care of running it!
2012-10-25Split reprepro::cron and reprepro::inotify to separate filesTails developers
2012-10-25Do not enforce permissions when manage_incoming_conf is falseTails developers
2012-10-25Leave more control to users when conf/distributions is not managedTails developers
If we do not manage conf/distributions, we should not call reprepro ourselves, the caller may change its content at other times than Puppet. We also should not enforce its permissions.
2012-10-23Refer to variables using Ruby instance variables in templatesTails developers
This is the recommended way, as it prevents clashes with Ruby function names.
2012-10-23Drop support for the venerable etchTails developers
2012-10-23Make basedir permissions configurable with $reprepro_basedir_mode.intrigeri
When one wants to use the reprepro login to upload packages to incoming, too lax permissions on its $HOME make sshd unhappy, and one wants to fix that.
2012-07-02Merge branch 'export-no-need-for-refreshonly'intrigeri
2012-07-02Drop useless refreshonly for resource that already has a "create" parameter.intrigeri
In production, this does not change anything worth noting. But when developing, being able to delete the exported pubkey and re-run Puppet is useful.
2012-07-02Merge branch 'improve-pubkey-export'intrigeri
2012-07-02Make sure the exported key is owned by reprepro:reprepro.intrigeri
2012-07-02Merge branch 'improve-pubkey-export'intrigeri
2012-07-02Make sure the exported public key is world-readable.intrigeri
2012-07-02Use a temporary file + atomic move when exporting the repository public key.intrigeri
2012-02-04Allow opting-out of conf/incoming's and conf/distributions' content management.intrigeri
Sometimes it's much simpler to manage these files outside of Puppet.
2012-01-31Install inoticoming from reprepro::inotify only.intrigeri
2012-01-31Add $reprepro_incoming_mode variable.intrigeri
This makes permissions of the reprepro incoming directory configurable.
2012-01-31Make distributions template not specific to Koumbit.intrigeri
2011-06-21fix startup script patternAntoine Beaupre
2011-06-21put cron in a separate classAntoine Beaupre
2011-06-21fix startup script to be explicitely for repreproAntoine Beaupre
2011-06-21add inotify class to start reprepro watcher on bootAntoine Beaupre
2011-06-21make repository origin customizeableAntoine Beaupre