gunghogeoduck/osem-fcy
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge c2e58490bd into 2f15309f0c

Browse source
This commit is contained in:
Paulo Barros 2016-03-21 17:42:11 +00:00
commit 2cb7dcd3e3
1 changed files with 12 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

18
INSTALL.md
View file

@ -20,34 +20,40 @@ We are using [Vagrant](https://www.vagrantup.com/) to create our development env
git clone https://github.com/openSUSE/osem.git git clone https://github.com/openSUSE/osem.git
``` ```
4. Execute Vagrant: 4. Navigate into your fork's directory, where the Vagrantfile is located:
```
cd osem
```
5. Execute Vagrant:
``` ```
vagrant up vagrant up
``` ```
5. Start your OSEM rails app: 6. Start your OSEM rails app:
``` ```
vagrant exec rails server -b 0.0.0.0 vagrant exec rails server -b 0.0.0.0
``` ```
6. Check out your OSEM rails app: 7. 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. 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!: 8. Changed something? Test your changes!:
``` ```
vagrant exec rake test vagrant exec rake test
``` ```
8. Explore the development environment: 9. Explore the development environment:
``` ```
vagrant ssh vagrant ssh
``` ```
9. Or issue any standard `rails`/`rake`/`bundler` command by prepending `vagrant exec` 10. Or issue any standard `rails`/`rake`/`bundler` command by prepending `vagrant exec`
``` ```
vagrant exec rake db:migrate vagrant exec rake db:migrate