-
Notifications
You must be signed in to change notification settings - Fork 24
/
Copy pathorigen_site_config.yml
158 lines (130 loc) · 6.58 KB
/
origen_site_config.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
# BROADCAST MESSAGES
# All broadcast messages will output to the console for all users every time Origen is invoked
#broadcast_info:
# - These lines will be output to the console in regular text
#broadcast_warning:
# - These lines will be output to the console in amber text
#broadcast_danger:
# - These lines will be output to the console in red text
#broadcast_success:
# - These lines will be output to the console in green text
# GENERAL SETUP
# Application generator plugins can be used to extend the available new application templates
# that are offered via the 'origen new' command.
# This allows you to offer application shells that are unique to your company or to specific
# domains within your company.
#app_generators:
# # Example of how to reference a plugin from an internal gem server (recommended)
# - ["http://gems.mycompany.net:9292", my_app_generators]
# # Alternatively a file system path to a central copy of a plugin can be used
# - "/path/to/some/central/location/my_app_generators"
# # Or a reference to a plugin's Git repository can be used
# - "http://bitbucket.mycompany.net/origen/my_app_generators.git"
# Centralized Site Config
# Origen +0.36 (versions after 36.0) supports a centralized site config. This site config will be implicitly read and
# injected into the site config following the default site configs from Origen.
# To surpress the number of requests and possible load time delays, the site config can be cached and read on each
# startup for :centralized_site_config_refresh number of hours.
centralized_site_config_cache_dir: '~/.origen/cache/site_config'
# Indicates how many hours should pass before the cached site config is refreshed (refetched, redownloaded)
# The default is to refresh once per day (every 24 hours). Decimal values can be used here to get more granularity
# if needed.
# 0 indidcates 'always refresh' (cache will still occur though)
# -1 indicates never refresh.
centralized_site_config_refresh: 24
# Indicates whether the SSL certificate should be verified when pulling the centralized site config
centralized_site_config_verify_ssl: true
# GEM SETUP
# If your company has an internal gem server enter it here:
#gem_server: https://gems.company.net:9292
# or here, if you need to use different urls for push and pull (write and read):
#gem_server_push: https://gems.company.net:9292
#gem_server_pull: https://gems.company.net:9292
# By default, the Origen 'rake gem:release' task (called by the 'origen rc tag' command), will use
# the standard Ruby 'gem push' command to push gems to your company gem server.
# If you need to use a different command, define it here as a string using, +GEM+ where you want
# the gem name to be referenced, and +URL+ to reference your company gem server.
#gem_push_cmd: "gem inabox --host +URL+ +GEM+"
#gem_push_cmd: "gem nexus +GEM+ --url +URL+ --clear-repo --ignore-ssl-errors"
# If your custom gem_push_cmd requires a gem plugin(s), add the gem names here and they will be
# included in new applications generated via the 'origen new' command.
#gem_push_plugins:
# - geminabox
# - nexus
# When true Origen will configure and run Bundler in a consistent way for every
# user (recommended)
gem_manage_bundler: true
# WORKSPACE DIRECTORY SETUP
# Defines where the home directory is
#home_dir: ~/
# Defines where the user customization directory is
#user_install_dir:
# Defines the gems are to be installed
#user_gem_dir:
# Indicates whether '.origen' should be appended to home_dir
append_dot_origen: true
# Indicates whether 'gems' should be appended to the user_gem_dir
append_gems: true
# ORIGEN STARTUP OPTIONS
# These options define how and where Origen should boot.
# See the guides at advanced/invocations for additional details.
# By default, don't allow user install. This is more for power users to utilize for debug or those who want absolute
# control over their environment.
user_install_enable: false
# Default 'tool_repo_install_dir' to nil, meaning no 'tool_repo_install_dir' is present. If neither this nor
# 'user_install_enable' is present, the universal install will be used.
#tool_repo_install_dir: nil
# If 'tool_repo_install_dir' is set, then, by default, Bundler will use and build the gems in the tool repo.
# Purpose of this, is to allow a power user to setup and install these gems and for individuals to just use.
# Added this parameter and set to true so that this will be the default behavior. Otherwise, gem_install_dir
# would need to be overwritten and set with the 'tool_repo_install_dir'
gems_use_tool_repo: true
# Some gems can be difficult to install reliably across individual user environments.
# Such gems can be installed to a communal system Ruby and then listed here, Origen
# will then use the system version of the given gem instead of trying to install
# it fresh for each user.
# Note that this option will only be applied if gem_manage_bundler is set to true.
gem_use_from_system:
- [nokogiri, 1.7.2]
- [nokogiri, 1.8.5]
# Additionally any build switches/options that are required to build specific gems
# in your user environment can be defined here.
#gem_build_switches:
# - nokogiri --use-system-libraries=true --with-xml2-include=/path/to/libxml2
# - other_gem --some_build_switch
# USERS AND LDAP
# Adding an email domain will allow email addresses for users to be automatically
# generated from their ID e.g.
#
# # With email_domain specified
# User.new("ax1234").email # => "[email protected]"
#
# # Without email_domain specified
# User.new("[email protected]").email # => "[email protected]"
# If authentication is needed to use the given server, email_authentication can be set to login.
# If a service user is used to access this account on behalf of the sending users, email_auth_user and email_auth_password
# can be set. If authentication is indicated but no auth user is given, the current user's email and password are used instead.
#email_domain: company.com
#email_server: smtp.company.net
#email_port: 25
#email_authentication: login
#email_auth_user: service_email
#email_auth_password: service_password
# Required parameters to connect to your company's LDAP system
#ldap_username: cn=manager,dc=example,dc=com
#ldap_password: opensesame
#ldap_host: ids.company.net
#ldap_port: 636
#ldap_base_dn: ou=people,ou=intranet,dc=com
# Optional to override the name given to the user ID attribute on the LDAP system ('id' by default)
#ldap_user_id_attribute: uid
# LSF Configuration
# lsf_queue: 'batchq'
# lsf_group: 'nil'
# lsf_project: 'msg.te'
# lsf_resource: 'rhel6'
# lsf_cores: '1'
# lsf_max_jobs: 400
# lsf_queue_count_only: false
# lsf_debug is needed for spec tests on the core.
lsf_debug: 'false'