Forge Home


atom (editor) installation with plugin support


6,485 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.0 (latest)
released Apr 3rd 2017
This version is compatible with:
  • Puppet Enterprise >= 3.8.0
  • Puppet >= 3.8.0
  • , , , , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'eyp-atom', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add eyp-atom
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install eyp-atom --version 0.1.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



eyp/atom — version 0.1.0 Apr 3rd 2017


Table of Contents

  1. Overview
  2. Module Description
  3. Setup
  4. Usage
  5. Reference
  6. Limitations
  7. Development


atom installation and plugin management

Module Description

This module can install the atom editor and manage it's plugins. By default (can be disabled by setting add_default_plugins to false) installs the following plugins:

  • aligner
  • aligner-puppet
  • atom-alignment
  • autocomplete-ruby
  • block-comment
  • dockerletion
  • git-plus
  • language-docker
  • language-puppet
  • language-rspec
  • linter
  • markdown-writer
  • minimap
  • minimap-git-diff
  • rspec-snippets


What atom affects

Setup Requirements

This module requires pluginsync enabled

Beginning with atom

class { 'atom':
  atom_user => 'jprats',


atom_plugin { 'language-puppet':
  ensure => 'present',
  atom_user => $atom::atom_user,




  • manage_package: manage atom package (default: true)
  • package_ensure: atom package ensure (default: installed)
  • srcdir: place to store temporal files (default: /usr/local/src)
  • add_default_plugins: whether to install default plugins (default: true)
  • atom_user: install plugins to this user (default: root)



  • name: atom plugin to manage
  • atom_user: (default: root)


Tested on:

  • Ubuntu 14.04
  • Ubuntu 16.04


We are pushing to have acceptance testing in place, so any new feature should have some test to check both presence and absence of any feature


nothing so far


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request