-
Notifications
You must be signed in to change notification settings - Fork 0
4. Open Source Maintenance and Communication
Kevin Marin edited this page Dec 8, 2020
·
1 revision
- Install Rails -v 6.0
- Install Ruby -v 2.7
- Install PostgreSQL -v 12.4
- Clone repository
On the src
directory type the following into the command prompt:
>ip addr show eth0
output
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 06:d3:6b:e0:6c:61 brd ff:ff:ff:ff:ff:ff
inet 10.18.6.11/24 brd 10.18.6.255 scope global noprefixroute dynamic eth0
valid_lft 40793sec preferred_lft 40793sec
inet6 fe80::4d3:6bff:fee0:6c61/64 scope link
valid_lft forever preferred_lft forever
Use the number after "inet" from previous output
>rails server --binding=10.18.6.11
- Issues and bugs shall be listed in Issues section with appropriate tags to address them. Members will assign priority by adding reactions.
- Future plans and ideas for the project shall be included in the Issues section with the "idea" tag. Ideas or future plans may be broken down into implementable steps, which after consideration by members will either be shelfed or given the green light as a reaction.
To contribute to the project:
- Make a new branch
- Add readme file that addresses:
- What issue, bug, idea are you addressing (include Issues number)
- How are you addressing the issue, bug, or idea
- Additional comments
- Test cases for new changes made as follows:
new changes or features | input | previous output | output |
---|---|---|---|
post does not show | post_entry | blank | post |
- Make a test file
- Create a pull request when you are ready
Members will routinely go through branches checking for contributions. Code that addresses an issue, bug, or idea (depending on whether idea has been green lighted) and follows clean and modular formatting will be accepted. If accepted, the branch where the contribution is made will be merged to the main branch.