search

OpenRepeater / documents

This is the main repository for the OpenRepeater Project where WIKIs and Issues live.
http://openrepeater.com
GNU General Public License v3.0
22 stars 8 forks source link

PHP App Discussion #8

Closed mathewpeterson closed 9 years ago

mathewpeterson commented 10 years ago

I was wondering what your plans for the php application. There are a few improvements that I see could be done right away but I think it would be a good idea to rebuild some of the code base with a framework so we can follow generally software engineering principles.

I do have quite a bit of PHP application experience and I would love to help out as much as I can.

abcrawford commented 10 years ago

I plan to make more improvements to the php interface. I just wanted to get what I have out there so others can start to test with it. There are a number of things that need polished and some other features added. The web application uses bootstrap framework. Let me know what you thoughts are and what type of framework you are thinking. I probably won't have much time to do anything until the beginning of August. This is step one, and I have practically had folks begging me for code.

mathewpeterson commented 10 years ago

I have quite a bit of experience with Symfony and Silex building large applications. But in any case, we can integrate Twitter Bootstrap into any of them.

How do you plan on setting up the github repositories? My recommendation would be to create an "openrepeater" organization and create different repositories for each piece:

openrepeater/webapp - php application openrepeater/hardware-designs - eagle files openrepeater/raspbian-image - raspbian build scripts (to automate the image building process)

abcrawford commented 10 years ago

@mathewpeterson, Thanks for the feedback. I would say my first priority when I get back at the beginning of August would be to setup the repositories. I'm fairly new to GitHub and have been trying to determine the best way to do things. I was already to the point where I have determined that I will need to separate the web app from the hardware files. I just didn't want to set things up one way then kick myself later for doing it wrong.

The organization for grouping sounds like a good idea. It would probably also make sense to have multiple hardware repositories ie for Raspberry Pi, Beaglebone Black, which are the two SBCs that I am currently testing on. There are some other ones coming down the pike too like the Cubieboard and the Banana Pi so it would make sense to future proof. That's why I changed the name of the project to from Raspberry Pi Repeater Project to OpenRepeater Project to not limit it to just one device while building "brand recognition".

Thanks for the feedback and I look forward to work with you!

mathewpeterson commented 10 years ago

That sounds good.

Is there any chance you could create the organization now and give me access to it? I could then help with getting the current code uploaded for others to see.

abcrawford commented 10 years ago

I will see what I can do, I am getting ready to go out of town for the week. If I don't get a chance this evening, I will hopefully do it while waiting for my plane.

mathewpeterson commented 10 years ago

Sounds good! Thanks for all your hard work!

abcrawford commented 10 years ago

OK, I just created the organization and added you to it. I transferred the existing repository and renamed it webapp. My lunch is over...so that is all I can do for now. Thanks.

mathewpeterson commented 10 years ago

This will help tremendously.

Can we rename the existing repo to OpenRepeater/OpenRepeater and create new repositories for everything else? This will help with keeping a clean git history. I can rename it if you would like.

abcrawford commented 10 years ago

That is fine. I'm going to lean on your GitHub expertise. Thanks.

On Jul 25, 2014, at 1:14 PM, Mathew Peterson notifications@github.com wrote:

This will help tremendously.

Can we rename the existing repo to OpenRepeater/OpenRepeater and create new repositories for everything else? This will help with keeping a clean git history. I can rename it if you would like.

— Reply to this email directly or view it on GitHub.

abcrawford commented 10 years ago

I already have the wikis under this one so whatever makes sense.

On Jul 25, 2014, at 1:14 PM, Mathew Peterson notifications@github.com wrote:

This will help tremendously.

Can we rename the existing repo to OpenRepeater/OpenRepeater and create new repositories for everything else? This will help with keeping a clean git history. I can rename it if you would like.

— Reply to this email directly or view it on GitHub.

abcrawford commented 10 years ago

Also, Svxlink recently moved from SourceForge to GitHub so I'd assume we can add a fork of it into the organization.

mathewpeterson commented 10 years ago

I have created a new repo (https://github.com/OpenRepeater/webapp), copied the code over from the raspbian image, and removed the images in img/gallery. I also did not include the svxlink program, that will be out of scope of the webapp repository and most likely handled by the raspbian build scripts.