| # Extended configuration for Thinking Sphinx can be stored in the | |
| # config/thinking_sphinx.yml file within your application (this file was | |
| # previously known as config/sphinx.yml in TS v1/v2). | |
| # | |
| # Many settings from Sphinx itself can be set here, and they'll flow through to | |
| # the appropriate section of the generated configuration. However, some are | |
| # used for Thinking Sphinx behaviour, and so those are documented here first. | |
| # | |
| # Configuration is grouped by environment, just like config/database.yml in a | |
| # standard Rails application. |
UPDATE (March 2020, thanks @ic): I don't know the exact AMI version but yum install docker now works on the latest Amazon Linux 2. The instructions below may still be relevant depending on the vintage AMI you are using.
Amazon changed the install in Linux 2. One no-longer using 'yum' See: https://aws.amazon.com/amazon-linux-2/release-notes/
sudo amazon-linux-extras install docker
sudo service docker start
Run rails new --help to see all of the options you can use to create a new Rails application:
Output for Rails 8+
Usage:
rails COMMAND [options]
You must specify a command:
This original document shows how to deploy an OpenShift instance on a server using CodeReady Containers (crc) that can be accessed remotely from one or more client machines (sometimes called a "headless" instance). This provides a low-cost test and development platform that can be shared by developers. Deploying this way also allows a user to create an instance that uses more cpu and memory resources than may be available on his or her laptop.
While there are benefits to this type of deployment, please note that the primary use case for crc is to deploy a local OpenShift instance on a workstation or laptop and access it directly from the same machine. The headless setup is configured completely outside of crc itself, and supporting a headless setup is beyond the mission of the crc development team. Please do not ask for changes to crc to support this type of deployment, it will only cost the team time as they politely decline :)
The original gist by Roberto ha
| #!/bin/bash | |
| # Simple script to help configuring which kn CLI to use when you | |
| # have a need to keep multiple versions and switch between them. | |
| # Install and notes: | |
| # 1. put this in /usr/local/bin and chmod +x | |
| # 2. keep all the versions of kn in the /Applications directory | |
| # 3. name kn executables with corresponding version - e.g. /Applications/kn-0.14.0 |
| # Get odo for linux | |
| $ curl -OL https://mirror.openshift.com/pub/openshift-v4/clients/odo/v2.0.0/odo-linux-amd64 && mv odo-linux-amd64 odo && chmod u+x odo | |
| $ export PATH=$PATH:$(pwd) | |
| $ odo version | |
| # Use git to check out the .NET Core application | |
| $ git clone https://github.com/redhat-developer/s2i-dotnetcore-ex | |
| $ cd s2i-dotnetcore-ex/app | |
| $ git checkout dotnetcore-3.1 |
| kind: ImageSetConfiguration | |
| apiVersion: mirror.openshift.io/v1alpha2 | |
| storageConfig: | |
| local: | |
| path: ./ | |
| mirror: | |
| platform: | |
| channels: |
