Web components have ports exposed to the external network making them publicly accessible. These should be used for any public-facing code component.
Overview of Web Component Settings in the Boxfile
web.site: # Start Command start: 'rails s' # Routing routes: - 'sub:/path/' - '/admin/' # Port Mapping ports: - tcp:21:3420 - udp:53:3000 # Network Storage network_dirs: data.files: - path/to/directoryA - path/to/directoryB data.unfs: - path/to/directoryC # Writable Dirs writable_dirs: - path/to/dirA - path/to/dirB # Custom Logs log_watch: app[error]: 'path/to/error.log' # Cron cron: - id: flush_cache schedule: '0 0 * * *' command: 'rm -rf app/cache/*' - id: echo_msg schedule: '*/3 */2 1-3 2,6,7 2' command: 'echo i\'m a little teapot' # Only provision component locally local_only: true
start is the command used to start your web process. **Required for all web components**
web.site: start: 'rails s'
Multiple start commands can be provided. The following formats are accepted:
web.site: start: 'rails s'
An array of strings
web.site: start: - 'rails s' - 'ruby monitor.rb'
An array of hashes
web.site: start: rails: 'rails s' monitor: 'ruby monitor.rb'
When using an array of hashes, the key is appended to the log output of the command, providing helpful context to log output. This format is recommended when using multiple start commands.
In some cases, you may want or need multiple web components within a single application. This allows you to isolate requests to specific subdomain or path in your application to an individual web component.
Web component routing in Nanobox is really flexible, allowing you to route based on subdomains, paths, or both. This feature is fully documented in the Routing to Web Components doc, but examples are shown below.
web.site: routes: - '/' # mydomain.com would route to web.sites web.admin: routes: - '/admin' # mydomain.com/admin would route to web.admin web.api: routes: - 'api:/' # api.mydomain.com would route to web.api web.api-auth: routes: - 'api:/auth/validate' # api.mydomain.com/auth/validate would route to web.api-auth
Nanobox allows to do define on which ports your web component listens for connections over tcp and udp protocols. More information is available in the Port Mapping doc.
Note: Your app must listen on port 8080 to connect to the public network over http/https.
# Pattern web.site: ports: - protocol:source:destination # Examples (Default) web.site: ports: - tcp:21:3420 - udp:53:3000
These directories are read/write accessible to all the web components's instances. These directories are mounted at runtime, and should not be created at the same location as a directory containing source code in your repo. Filepaths should be relative to the root of your repo.
In order to use
network_dirs, you must have one or more Network Storage components (unfs, gluster, etc.) in which to store them. In your Boxfile config, specify which storage component the directories should be stored on.
For more details, view the Network Storage doc.
web.site: network_dirs: data.files: - path/to/directoryA - path/to/directoryB data.unfs: - path/to/directoryC
Note: On deploy, network directories are replaced with network mounts, which connect code instances to your network storage component(s). These mounts obscure anything committed to your repo inside of those directories. If there are files inside network directories in your repo, your app will not be able to access them unless you manually upload them into your storage component.
These directories are read/write accessible and stored in each instance's local filesystem. These directories are mounted at runtime, and should not be created at the same location as a directory containing source code in your repo. Filepaths should be relative to the root of your repo.
web.site: writable_dirs: - path/to/dirA - path/to/dirB
For more details, view the Writable Directories doc.
Many apps and frameworks log to files stored in the file system.
log_watch's allow you to include any entries written to these log files in your unified log stream. More information is available in the Application Logs doc.
web.site: log_watch: key: path/to/log.file app[error]: app/logs/error.log
Cron is a time-based job scheduler that enables you to schedule jobs (commands) to run periodically at certain times or dates. Cron jobs specified in a component's boxfile config are loaded into the component's crontab. More information is available in the Cron Jobs doc.
# Pattern web.site: cron: - id: unique-identifier schedule: 'cron schedule' command: 'command' # Examples web.site: cron: - id: flush_cache schedule: '0 0 * * *' command: 'rm -rf app/cache/*' - id: echo_msg schedule: '*/3 */2 1-3 2,6,7 2' command: 'echo i\'m a little teapot'
In some cases, you may only want to provision a component when developing and testing locally. The
local_only config will provision the component when working locally (local and dry-run), but not when deploying to a live server.
Note: Web components are only provisioned and started locally in a dry-run envrionment.
web.site: # ... local_only: true
Reach out to email@example.com and we'll try to help.