Shell script to bootstrap Solaris 10 as a puppet node. Used with cloud computing architecture to instantiate and configure Solaris systems at first boot.
  • Shell 68.5%
  • Dockerfile 31.5%
Find a file
2026-04-27 23:04:38 +00:00
bootstrap-puppet-solaris.sh Initial commit 2011-10-05 12:59:31 +05:30
Dockerfile Add Dockerfile: Debian + puppet-agent for inspecting/cross-compiling the Solaris bootstrap script 2026-04-27 23:04:38 +00:00
nocheck Initial commit 2011-10-05 12:59:31 +05:30
README.md Update README with comprehensive project information 2026-04-27 20:39:28 +00:00

Solaris-Puppet-Node

Shell script to bootstrap Solaris 10 as a puppet node. Used with cloud computing architecture to instantiate and configure Solaris systems at first boot.

Overview

Solaris-Puppet-Node

Detected project type: Shell.

At a glance

  • Default branch: master
  • Visibility: public
  • Size: 27 KB
  • Created: 2026-04-16
  • Last updated: 2026-04-27
  • Stars / Forks / Open issues: 0 / 0 / 0

Languages

Language Bytes Share
Shell 1,268 bytes 100.0%

Repository structure

  • bootstrap-puppet-solaris.sh (1,268 B)
  • nocheck (148 B)
  • README.md (195 B)

Getting started

Clone the repository:

git clone https://forgejo.deployview.com/ssa/Solaris-Puppet-Node.git
cd Solaris-Puppet-Node

Installation

git clone https://forgejo.deployview.com/ssa/Solaris-Puppet-Node.git
cd Solaris-Puppet-Node

Usage

Refer to the source files in this repository for entry points and intended usage. Update this section with concrete examples once they are established.

Original README

The content below is preserved from the previous README. Headings have been demoted so they don't compete with the new top-level sections.

===================

Shell script to bootstrap Solaris 10 as a puppet node. Used with cloud computing architecture to instantiate and configure Solaris systems at first boot.

Contributing

Contributions are welcome. The typical workflow is:

  1. Open an issue describing the change you'd like to make.
  2. Fork the repository (or create a feature branch if you have write access).
  3. Commit your changes with clear, descriptive messages.
  4. Open a pull request against the master branch.

Please follow the existing code style and include tests or reproduction steps where relevant.

License

No LICENSE file is currently present in this repository. Treat the contents as all rights reserved by the author until an explicit license is added. If you intend to share or accept contributions, consider adding an OSI-approved license such as MIT, Apache-2.0, or GPL-3.0.

Repository


This README was generated automatically based on repository metadata, contents, and any prior README content. Edit any section above to add project-specific detail.