[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-7950":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":16,"stars30d":16,"stars90d":16,"forks30d":16,"starsTrendScore":16,"compositeScore":17,"rankGlobal":10,"rankLanguage":10,"license":18,"archived":19,"fork":20,"defaultBranch":21,"hasWiki":20,"hasPages":20,"topics":22,"createdAt":10,"pushedAt":10,"updatedAt":23,"readmeContent":24,"aiSummary":25,"trendingCount":16,"starSnapshotCount":16,"syncStatus":26,"lastSyncTime":27,"discoverSource":28},7950,"our-boxen","boxen\u002Four-boxen","boxen","Copy me for your team.","https:\u002F\u002Fgithub.com\u002Fboxen\u002Four-boxen\u002F",null,"Ruby",2570,857,4,3,0,30.8,"MIT License",true,false,"master",[],"2026-06-12 02:01:46","# Our Boxen\n\nThis is a template Boxen project designed for your organization to fork and\nmodify appropriately.\nThe Boxen rubygem and the Boxen puppet modules are only a framework for getting\nthings done.\nThis repository template is just a basic example of _how_ to do things with them.\n\n## Getting Started\n\nTo give you a brief overview, we're going to:\n\n* Install dependencies (basically Xcode)\n* Bootstrap a boxen for your self\u002Fteam\u002Forg\u002Fcompany\n* Then convert your local copy of that boxen to the post-bootstrapped version\n\nThere are a few potential conflicts to keep in mind.\nBoxen does its best not to get in the way of a dirty system,\nbut you should check into the following before attempting to install your\nboxen on any machine (we do some checks before every Boxen run to try\nand detect most of these and tell you anyway):\n\n* Boxen __requires__ at least the Xcode Command Line Tools installed.\n* Boxen __will not__ work with an existing rvm install.\n* Boxen __may not__ play nice with a GitHub username that includes dash(-)\n* Boxen __may not__ play nice with an existing rbenv install.\n* Boxen __may not__ play nice with an existing chruby install.\n* Boxen __may not__ play nice with an existing homebrew install.\n* Boxen __may not__ play nice with an existing nvm install.\n* Boxen __recommends__ installing the full Xcode.\n\n### Dependencies\n\n**Install the Xcode Command Line Tools and\u002For full Xcode.**\nThis will grant you the most predictable behavior in building apps like\nMacVim.\n\nHow do you do it?\n\n#### OS X 10.9 (Mavericks)\n\nIf you are using [`b26abd0` of boxen-web](https:\u002F\u002Fgithub.com\u002Fboxen\u002Fboxen-web\u002Fcommit\u002Fb26abd0d681129eba0b5f46ed43110d873d8fdc2)\nor newer, it will be automatically installed as part of Boxen.\nOtherwise, follow instructions below.\n\n#### OS X \u003C 10.9\n\n1. Install Xcode from the Mac App Store.\n1. Open Xcode.\n1. Open the Preferences window (`Cmd-,`).\n1. Go to the Downloads tab.\n1. Install the Command Line Tools.\n\n### Bootstrapping\n\nCreate a **new** git repository somewhere on the internet.\nIt can be private or public -- it really doesn't matter.\nIf you're making a repository on GitHub, you _may not_ want to fork this repo\nto get started.\nThe reason for that is that you can't really make private forks of public\nrepositories easily.\n\nOnce you've done that, you can run the following to bootstrap\nyour boxen:\n\n```\nsudo mkdir -p \u002Fopt\u002Fboxen\nsudo chown ${USER}:staff \u002Fopt\u002Fboxen\ngit clone https:\u002F\u002Fgithub.com\u002Fboxen\u002Four-boxen \u002Fopt\u002Fboxen\u002Frepo\ncd \u002Fopt\u002Fboxen\u002Frepo\ngit remote rm origin\ngit remote add origin \u003Cthe location of my new git repository>\ngit push -u origin master\n```\n\nNow that your boxen is bootstrapped, you can run the following to\ninstall the default configuration from this repo:\n\n```\ncd \u002Fopt\u002Fboxen\u002Frepo\n.\u002Fscript\u002Fboxen\n```\n\n### Distributing\n\nThat's enough to get your boxen into a usable state on other machines,\nusually.\nFrom there, we recommend setting up\n[boxen-web](https:\u002F\u002Fgithub.com\u002Fboxen\u002Fboxen-web)\nas an easy way to automate letting other folks install your boxen.\n\nIf you _don't_ want to use boxen-web, folks can get using your boxen like so:\n\n```\nsudo mkdir -p \u002Fopt\u002Fboxen\nsudo chown ${USER}:staff \u002Fopt\u002Fboxen\ngit clone \u003Clocation of my new git repository> \u002Fopt\u002Fboxen\u002Frepo\ncd \u002Fopt\u002Fboxen\u002Frepo\n.\u002Fscript\u002Fboxen\n```\n\nKeep in mind this requires you to encrypt your hard drive by default.\nIf you do not want to do encrypt your hard drive, you can use the `--no-fde`.\n\n```\n.\u002Fscript\u002Fboxen --no-fde\n```\n\nIt should run successfully, and should tell you to source a shell script\nin your environment.\nFor users without a bash or zsh config or a `~\u002F.profile` file,\nBoxen will create a shim for you that will work correctly.\nIf you do have a `~\u002F.bashrc` or `~\u002F.zshrc`, your shell will not use\n`~\u002F.profile` so you'll need to add a line like so at _the end of your config_:\n\n``` sh\n[ -f \u002Fopt\u002Fboxen\u002Fenv.sh ] && source \u002Fopt\u002Fboxen\u002Fenv.sh\n```\n\nOnce your shell is ready, open a new tab\u002Fwindow in your Terminal\nand you should be able to successfully run `boxen --env`.\nIf that runs cleanly, you're in good shape.\n\n## What You Get\n\nThis template project provides the following by default:\n\n* Homebrew\n* Homebrew-Cask\n* Git\n* Hub\n* dnsmasq w\u002F .dev resolver for localhost\n* rbenv\n* Full Disk Encryption requirement\n* Node.js 0.8\n* Node.js 0.10\n* Node.js 0.12\n* Ruby 1.9.3\n* Ruby 2.0.0\n* Ruby 2.1.8\n* Ruby 2.2.4\n* ack\n* Findutils\n* GNU tar\n\n## Customizing\n\nYou can always check out the number of existing modules we already\nprovide as optional installs under the\n[boxen organization](https:\u002F\u002Fgithub.com\u002Fboxen). These modules are all\ntested to be compatible with Boxen. Use the `Puppetfile` to pull them\nin dependencies automatically whenever `boxen` is run.\n\n### Including boxen modules from github (boxen\u002Fpuppet-\u003Cname>)\n\nYou must add the github information for your added Puppet module into your Puppetfile at the root of your\nboxen repo (ex. \u002Fpath\u002Fto\u002Fyour-boxen\u002FPuppetfile):\n\n    # Core modules for a basic development environment. You can replace\n    # some\u002Fmost of these if you want, but it's not recommended.\n\n    github \"repository\", \"2.0.2\"\n    github \"dnsmasq\",    \"1.0.0\"\n    github \"gcc\",        \"1.0.0\"\n    github \"git\",        \"1.2.2\"\n    github \"homebrew\",   \"1.1.2\"\n    github \"hub\",        \"1.0.0\"\n    github \"inifile\",    \"0.9.0\", :repo => \"cprice404\u002Fpuppetlabs-inifile\"\n    github \"nginx\",      \"1.4.0\"\n    github \"nodejs\",     \"2.2.0\"\n    github \"ruby\",       \"4.1.0\"\n    github \"stdlib\",     \"4.0.2\", :repo => \"puppetlabs\u002Fpuppetlabs-stdlib\"\n    github \"sudo\",       \"1.0.0\"\n\n    # Optional\u002Fcustom modules. There are tons available at\n    # https:\u002F\u002Fgithub.com\u002Fboxen.\n\n    github \"java\",     \"1.6.0\"\n\nIn the above snippet of a customized Puppetfile, the bottom line\nincludes the Java module from Github using the tag \"1.6.0\" from the github repository\n\"[boxen\u002Fpuppet-java\u002Freleases](https:\u002F\u002Fgithub.com\u002Fboxen\u002Fpuppet-java\u002Freleases)\".  The function \"github\" is defined at the top of the Puppetfile\nand takes the name of the module, the version, and optional repo location:\n\n    def github(name, version, options = nil)\n      options ||= {}\n      options[:repo] ||= \"boxen\u002Fpuppet-#{name}\"\n      mod name, version, :github_tarball => options[:repo]\n    end\n\nNow Puppet knows where to download the module from when you include it in your site.pp or mypersonal.pp file:\n\n    # include the java module referenced in my Puppetfile with the line\n    # github \"java\",     \"1.6.0\"\n    include java\n\n### Hiera\n\nHiera is preferred mechanism to make changes to module defaults (e.g. default\nglobal ruby version, service ports, etc). This repository supplies a\nstarting point for your Hiera configuration at `config\u002Fhiera.yml`, and an\nexample data file at `hiera\u002Fcommon.yaml`. See those files for more details.\n\nThe default `config\u002Fhiera.yml` is configured with a hierarchy that allows\nindividuals to have their own hiera data file in\n`hiera\u002Fusers\u002F{github_login}.yaml` which augments and overrides\nsite-wide values in `hiera\u002Fcommon.yaml`. This default is, as with most of the\nconfiguration in the example repo, a great starting point for many\norganisations, but is totally up to you. You might want to, for\nexample, have a set of values that can't be overridden by adding a file to\nthe top of the hierarchy, or to have values set on specific OS\nversions:\n\n```yaml\n# ...\n:hierarchy:\n  - \"global-overrides.yaml\"\n  - \"users\u002F%{::github_login}\"\n  - \"osx-%{::macosx_productversion_major}\"\n  - common\n```\n\n### Node definitions\n\nPuppet has the concept of a\n['node'](http:\u002F\u002Fdocs.puppetlabs.com\u002Freferences\u002Fglossary.html#agent),\nwhich is essentially the machine on which Puppet is running. Puppet looks for\n[node definitions](http:\u002F\u002Fdocs.puppetlabs.com\u002Flearning\u002Fagent_master_basic.html#node-definitions)\nin the `manifests\u002Fsite.pp` file in the Boxen repo. You'll see a default node\ndeclaration that looks like the following:\n\n``` puppet\nnode default {\n  # core modules, needed for most things\n  include dnsmasq\n\n  # more...\n}\n```\n\n### How Boxen interacts with Puppet\n\nBoxen runs everything declared in `manifests\u002Fsite.pp` by default.\nBut just like any other source code, throwing all your work into one massive\nfile is going to be difficult to work with. Instead, we recommend you\nuse modules in the `Puppetfile` when you can and make new modules\nin the `modules\u002F` directory when you can't. Then add `include $modulename`\nfor each new module in `manifests\u002Fsite.pp` to include them.\nOne pattern that's very common is to create a module for your organization\n(e.g., `modules\u002Fgithub`) and put an environment class in that module\nto include all of the modules your organization wants to install for\neveryone by default. An example of this might look like so:\n\n``` puppet\n# modules\u002Fgithub\u002Fmanifests\u002Fenvironment.pp\n\n class github::environment {\n   include github::apps::mac\n\n   include ruby::1-8-7\n\n   include projects::super-top-secret-project\n }\n```\n\n If you'd like to read more about how Puppet works, we recommend\n checking out [the official documentation](http:\u002F\u002Fdocs.puppetlabs.com\u002F)\n for:\n\n * [Modules](http:\u002F\u002Fdocs.puppetlabs.com\u002Flearning\u002Fmodules1.html#modules)\n * [Classes](http:\u002F\u002Fdocs.puppetlabs.com\u002Flearning\u002Fmodules1.html#classes)\n * [Defined Types](http:\u002F\u002Fdocs.puppetlabs.com\u002Flearning\u002Fdefinedtypes.html)\n * [Facts](http:\u002F\u002Fdocs.puppetlabs.com\u002Fguides\u002Fcustom_facts.html)\n\n### Creating a personal module\n\nSee [the documentation in the\n`modules\u002Fpeople`](modules\u002Fpeople\u002FREADME.md)\ndirectory for creating per-user modules that don't need to be applied\nglobally to everyone.\n\n### Creating a project module\n\nSee [the documentation in the\n`modules\u002Fprojects`](modules\u002Fprojects\u002FREADME.md)\ndirectory for creating organization projects (i.e., repositories that people\nwill be working in).\n\n## Binary packages\n\nWe support binary packaging for everything in Homebrew, rbenv, and nvm.\nSee `config\u002Fboxen.rb` for the environment variables to define.\n\n## Sharing Boxen Modules\n\nIf you've got a Boxen module you'd like to be grouped under the Boxen org,\n(so it can easily be found by others), please file an issue on this\nrepository with a link to your module.\nWe'll review the code briefly, and if things look pretty all right,\nwe'll fork it under the Boxen org and give you read+write access to our\nfork.\nYou'll still be the maintainer, you'll still own the issues and PRs.\nIt'll just be listed under the boxen org so folks can find it more easily.\n\n## upgrading boxen\nSee [FAQ-Upgrading](https:\u002F\u002Fgithub.com\u002Fboxen\u002Four-boxen\u002Fblob\u002Fmaster\u002Fdocs\u002Ffaq.md#q-how-do-you-upgrade-your-boxen-from-the-public-our-boxen).\n\n## Integrating with Github Enterprise\n\nIf you're using a Github Enterprise instance rather than github.com,\nyou will need to set the `BOXEN_GITHUB_ENTERPRISE_URL` and\n`BOXEN_REPO_URL_TEMPLATE` variables in your\n[Boxen config](config\u002Fboxen.rb).\n\n## Halp!\n\nSee [FAQ](https:\u002F\u002Fgithub.com\u002Fboxen\u002Four-boxen\u002Fblob\u002Fmaster\u002Fdocs\u002Ffaq.md).\n\nUse Issues or #boxen on irc.freenode.net.\n","Our Boxen 是一个基于 Ruby 的模板项目，旨在帮助组织通过 fork 和自定义来构建适合自身需求的开发环境。它利用 Boxen gem 和 Puppet 模块作为框架，提供了一个基础示例展示如何使用这些工具自动化设置和维护开发环境。项目支持从安装依赖（如Xcode）到引导个性化Boxen环境的全过程，并且强调了与现有某些软件（如rvm, rbenv等）可能存在的兼容性问题。适用于需要统一团队成员开发环境配置的企业或团队，特别是那些希望减少手动配置工作量、提高开发效率的情况。",2,"2026-06-11 03:15:20","top_language"]