- Unofficial Records - Compare your record time with other cubers in the Philippines. We will verify your record time and post it on the unofficial Philippine records list
- Learning Resources - Share algorithms and checkout the algorithm database. Watch/Read puzzle solving tutorials
- Events - Check upcoming official competitions and see results online. View the calendar for cubemeets near you
- Group Discussions - Participate in online group discussions about your favorite puzzles
- User Profiles - Contribute to the community and earn badges. Post your personal bests and tell something about yourself
- Online Competitions - Compete online with your friend on your favorite puzzles in real time. Host and join a competition using the web interface
- Cube Meets - Set and join meetups. View upcoming and past cube meets.
Instructions for Windows. Sorry, I am a .NET dev as well. Can't get away with windows.
-
Install Cygwin and setup system path. You could also use Windows Command Prompt.
e.g. C:\cygwin64\bin
Don't forget to choose the following packages :
- chere: Cygwin Prompt Here context menus
- make: The GNU version of 'make' utility
- openssh: The OpenSSH server and client programs
-
Install Vagrant and VirtualBox
-
Clone repository
git clone git@github.com:drfb/pinoycubers.git
-
Right click the
pinoycubers
folder and clickBash Prompt Here
-
Run
composer install
to install all project dependencies. Make sure you have composer installed.composer install
-
While on the cygwin terminal. Type this:
vagrant up
-
Add pinoycubers.dev to host file. (Use the exact IP address)
10.0.0.101 pinoycubers.dev
-
Enter Vagrant's ssh
vagrant ssh
-
Migrate and seed the database
cd /vagrant php artisan migrate --seed
host - 127.0.0.1
username - root
password - root
port - 3308
- When planning a pull-request to add new functionality, it may be wise to submit a proposal to ensure compatibility with the project's goals.
- I suggest using Vagrant for development environment configuration
- You may use Crunchapp or Prepros for compiling less files. We only need to compile
bootstrap.less
andsite.less
- I prefer PHPStorm for an IDE. Sublime Text 3 for an editor.
-
Why is this change necessary?
This question tells what to expect in the commit, to easily identify and point out unrelated changes.
-
How does it address the issue?
Describe, at a high level, what was done to affect change. Here are some good examples:
Introduce a red/black tree to increase search speed Remove <X>, which was causing <specific description of issue introduced by X>
If your change is obvious, you may be able to omit addressing this question.
-
The body should provide a meaningful commit message, which uses the imperative, present tense "change", not "changed" or "changes". See example in #2
This code is maintained by Philippine Cubers Association
New BSD License
Copyright (c) 201, Pinoy Cubers Association
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of Pinoy Cubers Association nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.