Organize Your GitHub Stars With Ease
PHP CSS Vue JavaScript HTML ApacheConf
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
app Fix galileo filter as the Star module no longer exists on the client (#… Nov 17, 2016
bootstrap Add PSR-2 code style May 21, 2016
config
database Refactoring of API Responses (#48) Jun 12, 2016
laradock @ f1716a2 Added Docker support with Laradock (#81) Sep 19, 2016
public Fix galileo filter as the Star module no longer exists on the client (#… Nov 17, 2016
resources
routes
storage
tests
.editorconfig
.env.example
.eslintrc Add linter for all .js and .vue files, correct all current linting is… Jul 29, 2016
.gitattributes Inital 5.2 and vuejs commit Jan 17, 2016
.gitignore
.gitmodules
.php_cs Use laravel CS defaults May 31, 2016
.styleci.yml
.travis.yml Add travis config Jan 18, 2016
LICENSE
artisan Inital 5.2 and vuejs commit Jan 17, 2016
composer.json Laravel 5.3 Shift (#92) Nov 15, 2016
composer.lock
gulpfile.js Hot Module Reloading (#112) Nov 13, 2016
karma.conf.js Mutation improvements and tests (#53) May 26, 2016
package.json Begin working on transitions Nov 16, 2016
phpunit.xml Inital 5.2 and vuejs commit Jan 17, 2016
readme.md Update readme.md Nov 21, 2016
server.php PSR updates May 31, 2016
yarn.lock Merge branch 'master' into ui-transitions Nov 16, 2016

readme.md

Astral v2

Join the chat at https://gitter.im/astralapp/astral Build Status

This is the repository for Astral v2. Currently looking for core contributors!


Improvements

  • Improved Caching
  • Improved UI/UX
  • Built on Laravel 5.3
  • Switched the front-end from AngularJS to VueJS

Getting up and running

With Homestead

  • Fork this repository, clone it, and cd into it
  • Install the front-end dependencies: yarn
  • Install the PHP dependenices: composer install
  • Install Homestead
  • Configure Homestead: homestead edit

    [...]
    
    folders:
        - map: ~/<PATH TO REPO>
          to: /home/vagrant/astral
    
    sites:
        - map: astralapp.app
          to: /home/vagrant/astral/public
    
    databases:
        - astral
    
     [...]
    
  • Add the local development domain to your hosts file: 192.168.10.10 astralapp.app
  • Create a new GitHub personal access token, and grab the keys it gives you
  • Copy the .env.example file and rename it to .env. Add your GitHub keys to it
  • SSH into your Homestead app, migrate the DB, and generate a new app key

    $ homestead ssh
    $ cd astral
    $ php artisan migrate
    $ php artisan key:generate
    
  • Fire up the app! Open a browser at http://astralapp.app/ and bask in its glory!

With Docker using Laradock

  • Fork this repository, clone it recursively including submodules, and cd into laradock folder
  • Execute Docker Compose: docker-compose up -d nginx mysql redis
  • Run a terminal inside workspace container: docker-compose exec workspace bash
  • Change to laradock user: su laradock
  • Install the front-end dependencies: npm install
  • Install the PHP dependencies: composer install and exit container
  • Add the local development domain to your hosts file: your_ip astralapp.app
  • Create a new OAuth Application, and grab the keys it gives you
  • Copy the .env.example file and rename it to .env. Add your GitHub keys to it
  • Run a terminal into your workspace container again, migrate the DB, and generate a new app key

    $ php artisan migrate
    $ php artisan key:generate
    
  • Fire up the app! Open a browser at http://astralapp.app/ and bask in its glory!

Compiling JavaScript and SCSS Changes

Astral uses JS and SCSS that needs to be transpiled before use. There are various NPM tasks available to you to make this easy.

  • When developing you often want to watch files for changes, and re-bundle automatically. You'll want to run either npm run watch-build or gulp watch (both do the same thing).
  • To get the bundle production ready, run npm run build-prod. This will clean out the build folder, and then generate the new production-ready JS and CSS assets.
  • Consult the package.json file for other NPM scripts you can use.

Contributing

  • Get up and running
  • Create a new descriptively-named branch
  • Commit your changes and push to your fork.
  • Create a pull request with a clear, well written description of what the PR is all about. You should always run npm run build-prod and commit the results before creating the PR.
  • Party!!