gunghogeoduck/osem-fcy
1
0
Fork 0
mirror of https://github.com/openSUSE/osem.git synced 2026-08-13 19:54:02 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Get rid of vagrant

Browse source 
We are using Docker now instead.

Closes https://github.com/openSUSE/osem/issues/1213
This commit is contained in:
Ana María Martínez Gómez 2019-02-21 13:42:21 +01:00 • committed by Ana María Martínez Gómez
parent 51f6ad6d14
commit 0aa49e9c64
6 changed files with 1 additions and 171 deletions
Download patch file Download diff file Expand all files Collapse all files

42
CONTRIBUTING.md
View file

@ -66,48 +66,6 @@ sed "s/13042/`id -u`/" docker-compose.override.yml.example > docker-compose.over
docker-compose exec osem_1 /bin/bash -l
```
### with Vagrant
Another option is using [Vagrant](https://www.vagrantup.com/) and [VirtualBox 5.0.10](https://www.virtualbox.org/wiki/Download_Old_Builds_5_0) to create your development environment.
1. Install [vagrant-exec](https://github.com/p0deje/vagrant-exec):
```bash
vagrant plugin install vagrant-exec
```
1. Start the development environment
```
vagrant up
```
1. Start OSEM inside the development environment
```
vagrant exec /vagrant/bin/rails server -b 0.0.0.0
```
6. Check out your OSEM rails app:
You can access the app [localhost:3000](http://localhost:3000). Whatever you change in your cloned repository will have effect in the development environment. Sign up, the first user will be automatically assigned the admin role.
7. Changed something? Test your changes!:
```
vagrant exec bundle exec rspec spec
```
9. Issue any standard `rails`/`rake`/`bundler` command
```
vagrant exec bundle exec rake db:migrate
```
8. Or explore the development environment:
```
vagrant ssh
```
## How to contribute translations
Please refer to our [translation guide](https://github.com/openSUSE/osem/wiki/Translation) in the wiki.