Mojolic...LConfig(3)

🎀 Mojolic...LConfig(3) 🎀

okay bestie, welcome to the Mojolic...LConfig(3) page — it’s from User Contributed Perl Documentation, and we’re about to make YAML config make sense. no cap.

✨ NAME ✨

Mojolicious::Plugin::NotYAMLConfig — Not quite YAML configuration plugin. It’s giving “YAML but make it Perl,” and honestly? iconic.

🌸 SYNOPSIS 🌸

Here’s the vibe, copy-paste style, so keep it exact:

# myapp.yml (it's just YAML with embedded Perl)
---
foo: bar
baz:
  - ♥
music_dir: <%= app->home->child('music') %>

# Mojolicious
my $config = $app->plugin('NotYAMLConfig');
say $config->{foo};

# Mojolicious::Lite
my $config = plugin 'NotYAMLConfig';
say $config->{foo};

# foo.html.ep
%= config->{foo}

# The configuration is available application-wide
my $config = app->config;
say $config->{foo};

# Everything can be customized with options
my $config = plugin NotYAMLConfig => {file => '/etc/myapp.conf'};

🦋 DESCRIPTION 🦋

So Mojolicious::Plugin::NotYAMLConfig is a YAML configuration plugin that preprocesses its input with Mojo::Template. By default it uses CPAN::Meta::YAML for parsing — and lowkey, that’s not the best YAML module available, but it’s good enough for most config files. If you need something more correct, you can use a different module like YAML::XS with the module option. slay.

The application object can be accessed via $app or the app function. A default configuration filename in the application home directory will be generated from the value of moniker in Mojolicious ($moniker.yml). You can extend the normal configuration file $moniker.yml with mode specific ones like $moniker.$mode.yml, which will be detected automatically. cute.

These configuration values are currently reserved:

• config_override — If this configuration value has been set in config in Mojolicious when this plugin is loaded, it will not do anything besides loading deployment specific plugins.
• plugins — One or more deployment specific plugins that should be loaded right after this plugin has been loaded.

For plugins, the shape is:

plugins:
  - SetUserGroup:
      user: sri
      group: staff

The code of this plugin is a good example for learning to build new plugins, you’re welcome to fork it.

See PLUGINS in Mojolicious::Plugins for a list of plugins that are available by default.

💅 OPTIONS 💅

Mojolicious::Plugin::NotYAMLConfig inherits all options from Mojolicious::Plugin::JSONConfig and supports the following new ones.

🔧 module 🔧

# Mojolicious::Lite
plugin NotYAMLConfig => {module => 'YAML::PP'};

Alternative YAML module to use for parsing.

🌈 METHODS 🌈

Mojolicious::Plugin::NotYAMLConfig inherits all methods from Mojolicious::Plugin::JSONConfig and implements the following new ones.

🧚 parse 🧚

$plugin->parse($content, $file, $conf, $app);

Process content with render in Mojolicious::Plugin::JSONConfig and parse it with CPAN::Meta::YAML.

sub parse ($self, $content, $file, $conf, $app) {
  ...
  $content = $self->render($content, $file, $conf, $app);
  ...
  return $hash;
}

🎀 register 🎀

my $config = $plugin->register(Mojolicious->new);
my $config = $plugin->register(Mojolicious->new, {file => '/etc/foo.conf'});

Register plugin in Mojolicious application and merge configuration.

👑 SEE ALSO 👑

• Mojolicious
• Mojolicious::Guides
• <https://mojolicious.org>

---

okay that’s the whole page, bestie 💖 this was Mojolic...LConfig(3) from perl v5.42.0, dated 2026-07-15. periodt ✨