A place to discover art markets in your area or an area you're looking to visit.
This project makes us of several global installations. The instructions for each global dependency is a link at the bottom of this README file.
This project's work flow uses feature branch work flow by utilizing git.
In a new directory preform a git init and a git pull request:
$ cd path/to/new/root/directory
$ git init
$ git pull https://github.com/Maumasi/local_art.gitAfter pulling down the project the dependencies need to be installed and configured.
$ npm install
$ composer installAfter these lines are executed you will be promoted with Creating the "app/config/parameters.yml" file where you will configure the project credentials. All the credentials requested have defaults, you will have to provide the credentials you intend to use. The only default parameter that should not be changed is image_upload_directory. Also, the mailer_* parameters are not being used in this project but have been left in for future expansion.
Using the parameters provided from the installation enter the following commands to build the database and configure tables:
$ app/console doctrine:database:create
$ app/console doctrine:schema:update --forceNote:
If there are errors creating a database, carefully read the error message(s), make sure your database port is running, and check your parameters you provided during installation in ROOT/app/config/parameters.yml
To start the built in server execute the following command:
$ app/console server:runYou can run the server on any IP:port of your choosing by declaring it with the `server:run` command like so: ```bash # run on localhost with port: 8908 $ app/console server:run 127.0.0.1:8908 ```
At this point the project should be up and running without any errors.
The directories that are going to be worked in the most, in the order your IDE will likely order them, are:
-
ROOT/app -
ROOT/devAssests -
ROOT/src -
ROOT/web
Models are known as Entities in Symfony. All entity classes are defined in ROOT/src/AppBundle/Entity/
Every entity class makes efficient use of Annotations. If you're not familiar with Annotations and how to use them check out Annotations in the Resources section.
Some entities have custom database query methods. These methods are located in ROOT/src/AppBundle/Repository
If there is a need to create complex database queries make a class for the query methods that extends a base class of EntityRepository if one does not already exist. If you are not familiar with Symfony's Doctrine/ORM queries, check it out in the Resources.
Symfony's form classes are located in ROOT/src/AppBundle/Form
Forms can be mapped to an entity class for processing using the configureOptions() method in the form class:
class ArtistRegitration extends AbstractType
{
public function buildForm(FormBuilderInterface $builder, array $options)
{
$builder
->add('firstName')
->add('lastName')
->add('profileImage', FileType::class, [
'required' => true,
])
->add('email', EmailType::class)
->add('nakedPassword', RepeatedType::class, [
'type' => PasswordType::class,
])
->add('businessName', TextType::class, [
'empty_data' => null,
'required' => false,
])
->add('website', UrlType::class, [
'empty_data' => null,
'required' => false,
])
->add('bio', TextType::class, [
'empty_data' => null,
'required' => false,
]);
}
public function configureOptions(OptionsResolver $resolver)
{
$resolver->setDefaults([
'data_class' => Artist::class,// <-- form mapped to the Artist entity
'validation_groups' => ['Default', 'registration'],
]);
}
}Note:
If you're not familiar with Symfony's form builder check it out in the Resources section.
Views are found in ROOT/app/Resources/views/
In this directory there are a few subdirectories that help organize the Twig components.
Views are build in components using Twig as the front-end framework. If you're not familiar with Twig check it out in the Resources section.
base.html.twig
This file holds the base HTML wrapper for every view.
common/
This directory holds all the components that will be used across multiple pages such as the <header> or the <footer>.
main/
This directory holds all the views that a site visitor can see
secure/
This directory holds all the components that will require an HTTPS protocol. These are the views that deal with user credentials.
Controllers are found in ROOT/src/AppBundle/Controller/
The MainController.php manages all the routes and data the site visitor uses.
Secure controllers are in the subdirectory Secure/
These controllers manage the routes and data for the account holders.
Fixtures provide fake data to the database to aid with development and testing.
To add or edit the fixtures go to ROOT/src/AppBundle/DataFixtures/ORM/fixtures.yml
When creating a fixture or editing a fixture, only parameters defined in the entity can be used.
YAML uses a tab deliniated scope, so be carefule with white space.
AppBundle\Entity\User: # Entity
user_{1..10}: # number of instances (10 users)
email (unique): <freeEmail()>
nakedPassword: '123qwe'
createdAt: <dateTime()>
# roles: 'ROLE_USER' <-- commented outNote:
If your note familiar with fixtures check it out in the Resources section.
SASS provides a way for CSS to be dynamic and DRY (Don't Repeat Yourself)
SASS files are located in ROOT/devAssets/sass
There are several subdirectory in this path to help keep the styles organized but all SASS files are imported into one single SASS file.
// styles.sass
// Google fonts
// =================================================
@import url('https://fonts.googleapis.com/css?family=Lato|Open+Sans|Raleway|Roboto|Slabo+27px')
// base settings
// =================================================
@import "util/reset"
@import "util/base"
@import "util/mixin"
@import "util/var"Any new SASS files need to be imported to the styles.sass file.
If you're not familiar with SASS, check it out in the Resources section.
In this project the one of the main jobs of Javascript is to handle the Google Maps API
ES6 scripts are located in ROOT/devAssets/Javascript/ES6.
The main scripts are located at the directory, all supporting scripts are in the subdirectory lib. Inside lib are several more subdirectories to help organize scripts by what they are or what they do.
Example:
ES6/
- app.js
- lib/
- classes/
- Map.js
- functions/
- mapOptions.js
- types/
- constants.jsthese scripts do not have to be written in ES6, but if you would like to get up to date with what you can do with ES6 check it out in the Resources section.
Gulp is a great and easy to use productivity tool.
The grunt script is located at ROOT/gulpfile.js
In this project Gulp is being used to trans-pile SASS into CSS and sends it to the ROOT/web/css public directory. It also trans-piles ES6 into legacy Javascript, concatenating all trans-piled Javascript files and then uglifing Javascript and creating a file in the ROOT/web/js public directory.
Example:
const gulp = require('gulp'),
sass = require('gulp-sass'),
babel = require('gulp-babel'),
uglify = require('gulp-uglify'),
concat = require('gulp-concat');
// compile SASS files
gulp.task('sass', () => {
// ... some gulp logic ...
});
// compile ES6 to legacy Javascript
gulp.task('compileES6', () => {
// ... some gulp logic ...
});
// compress all js files into one file
gulp.task('compressAllJS', ['compileES6'], () => {
// ... some gulp logic ...
});
// uglify the compiled ES6
// This gives us a chance to make changes to the compiled ES6 if we need to
gulp.task('uglyJS', ['compressAllJS'], () => {
// ... some gulp logic ...
});
// watch for sass file changes on save
gulp.task('watch', () => {
gulp.watch(['./devAssets/sass/**/*.sass', './devAssets/Javascript/ES6/**/**/*.js'], ['sass', 'uglyJS']);
});
gulp.task('default', ['sass', 'uglyJS', 'watch']);Some of the gulp tasks have a dependency on another task finishing first, so those dependent tasks are called in an array before the self-evoking anonymous function. The watch task monitors an array of file paths for changes when they are saved.The default task calls the tasks that end up running all the defined tasks.
To run the default gulp task execute the following command:
# yup, that's it
$ gulpNote: If you're not familiar with Gulp.js, check it out in the Resources section.