- Implementation of init command started.
- Current status:
- Decode and parse credentials – done
- Gather Git Repository URL using git gem – done
- Write deploy.rb
- Capify project
- deploy.rb now creates a symlink to database.yml with -f (force) and overwrites an eventually existing database.yml from the customer’s repository.
- Added travis testing meta data.
- Added RSpec tests for basic functionality.
- Fixed a Ruby 1.9.x issue.
- Enhanced error messages for invalid application tokens.
- Initial README.
- 0.4.0 has become 0.1.0 since features have been added.
- Added Railshoster Bundler settings to generate binstubs. Hence you don’t have to use “bundle exec” all the time. See http://gembundler.com/deploying.html for more details.
- Bugfix reagarding to keyboard input when no directory is given.
- Added capistrano task “railshoster:appurl” to show the default railshoster app url.
- “railshoster deploy” now can only be invoked if there’s a Capfile and a deploy.rb.
- Added “railshoster appurl” show the default railshoster app url. This command can only be invoked if there’s a Capfile and a deploy.rb.
- It now shows the appurl after invoking “railshoster deploy”.
- Fixed deploy_to path in deploy.rb
- Added flag for init command to pass app credentials via json hash such as:
railshoster init -json '{"t":"h","u":"user999999999","a":"rails1","h":"zeta.railshoster.de","p":"mypass"}' .
- Updated ROADMAP
- Added bundler as railshoster gem dependency to avoid problems with “rake” vs “bundle exec rake”.
- SSH publick key file recognition and upload to authorized_keys to enable a passwordless deploy.rb.
- Now also works for RailsHoster VPS (virtual Servers).
- Bugfix in deploy.rb.
- Splited up init_command into several helper modules to keep the InitCommand classes’ main workflow clear and obvious.
- Analysis of Gemfile.lock to determine your database adapter to modify database.yml.
- Refactored product specific settings.
- Moved from deploy.rb.yml into init_comand. added database.yml update via sftp
- Added a more meaningful error message when being invoked with a non-git repo.
- Updated message when there’s no compatible database gem in Gemfile.lock.