Changes to Puppet: Ruby etc

[sebb <se...@gmail.com>]

At preset the required version of ruby (e.g. 2.5) is linked to
/usr/local/bin/ruby2.5 and various config files have to be editted to use
that.

Would it be simpler to link the appropriate version of ruby to
/usr/local/bin/ruby and then use the generic path in configuration files
such as whimsy-pubsub.conf and cronjobs.pp?

Also, /srv/whimsy is populated directly from git, rather than using rake.
This means it is set up early on.

It seems to me that one could do the same for /srv/git/letsencrypt.
This would make it easier to request the SSL certificate as one would not
have to install rake first (or run git clone manually).

Sebb

Re: Changes to Puppet: Ruby etc

[Matt Sicker <bo...@gmail.com>]

Simplifying the ruby setup sounds useful. It can also help match the
equivalent Docker image more easily.

Whether or not you'll have library conflicts, though, I have no idea.

On Mon, 6 Jan 2020 at 14:45, sebb <se...@gmail.com> wrote:
>
> At preset the required version of ruby (e.g. 2.5) is linked to
> /usr/local/bin/ruby2.5 and various config files have to be editted to use
> that.
>
> Would it be simpler to link the appropriate version of ruby to
> /usr/local/bin/ruby and then use the generic path in configuration files
> such as whimsy-pubsub.conf and cronjobs.pp?
>
> Also, /srv/whimsy is populated directly from git, rather than using rake.
> This means it is set up early on.
>
> It seems to me that one could do the same for /srv/git/letsencrypt.
> This would make it easier to request the SSL certificate as one would not
> have to install rake first (or run git clone manually).
>
> Sebb



-- 
Matt Sicker <bo...@gmail.com>