OctoberCMS

Quick overview of setting up a OctoberCMS setup. I followed: http://erikaybar.name/octobercms-my-first-encounter/

Started up homestead: homestead up

Logged into homestead: ssh homestead – Created folder in my /Code/ folder for new project.

Ran the composer install to install vendor items and plugins: composer install

Added database and user for database in cpanel for the production site

Ran the October: php artisan october:up

 

Environments:

 

I setup on my local development to the newly created file I made in the root: .env

APP_ENV=dev           In the /config/ folder I added a /dev/ folder for the files for it to load for the local development environment specs.  I place s copy of the database file.

 

Git – Bolt

 

.gitignore for bolt I have:

!.htaccess
app/cache/**

But you still need the cache directory so I then add a file in the cache folder as a place holder…  I added the file and then ran this: git add app/cache/cacheholder.txt

 

009 – laravel and git tips

 

Great Resource : http://laravel-recipes.com/recipes/31/managing-your-project-with-git

  • Within the project folder, Setup new git repository as git  ::  git init
  • Add new files to get by ::  git add .  (When using init, most of the directories will be added automatically.)
  • Add remote repository link by :: git remote add origin https://github.com/user/gitname.git
  • Commit new files  ::  git commit -m “Initial commit, pushing first upload to git”
  • Pushing changes to the github repository :: git push origin master

Making changes

  • Add changes to the local git :: git add file.php   or all files git add .
  • Commit the changes :: git commit -m “New changes”
  • Push to github :: git push origin master

Getting new changes

  • Load new changes from master at github  ::  git fetch
  • Load new changes from master on local host is :: get pull
  • Merge new changes to your local repository  ::  git merge origin/master
  • OR you can do both of these at the same time  ::  git pull origin master

Undo a change

Adding to other computer or server

Cpanel hosting with a2hosting :: https://www.a2hosting.com/kb/developer-corner/php/installing-composer

Run the :: composer install  command in the directory

Setup the right PHP we frustrating.  The cpanel update”r” wouldn’t update so I had to add the info to the htaccess page: https://www.a2hosting.com/kb/developer-corner/php/using-alternate-php-versions#Method-1.3A-Use-cPanel

<IfModule mod_suphp.c>
  AddHandler application/x-httpd-php-5.5.0 .php
</IfModule>

Setup artisan on shared host:

https://www.a2hosting.com/kb/installable-applications/manual-installations/laravel1

Run the artisan key:generate command… didn’t work on the shared host, so I manually added on. int eh config/app.php file.

 

Day 008 – Coming together

Today I worked on finalizing Git from the last post, and update that post.

After, I decided to get a new project that I can tweak as I learn.  It will include a login, database use, etc…  maybe billing in the future.  That might be fun charging myself for something.

I was able to the tutorial from 5.1 and help from this guy.  I will be going to his site again for sure.

I was able to get a Laravel system up, add it to a new git, update the git, add the git to a different computer.  Nice, now I can develop on both my machines… Well almost.  It looks like one directory did not get added to the git repository.  I will work on adding that tomorrow morning.

Day 007 – Git more – PyroCMS

Getting Git all setup was not that hard.  There are a ton of how-tos especially from Git.

To setup a new git I use command and the Github App.  I like the visual concept, but both are really confusing still yet compared to what I’m use to from SVN.

I created a new git by going into the new Laravel install folder and typed: “git init” . From the app, I was then able to publish.  The app created the new repository.  Then I started with my first minor update.  I created a branch and change the first view.  I’m wiring this a few minutes after and I still can’t tell you how I did it.  I then uploaded the changes to the master at Git.  I then created a second branch that I will plan on making additional changes today.  I will try to update the master nightly as practice.

 

I installed Git, but ran into an idea or concept of running Laravel front-end and WordPress backend for users to add/edit content.  I searched and found that people were trying this.  But then I ran into a new CMS built on Laravel: PyroCMS.  I then spent nearly 2 hours trying to get the version 3 beta up an running.  I’m still stuck trying got install it homestead but cant get around the it not connecting to a database (sqlite) in homestead.  Arrrg.  I was trying to get SQLite, but then switched to MySQL… and surprisingly was easy just login to the database from “homestead ssh”.  I had to create a new database for PyroCMS.

Day 006 – Reboot

I decided to roll with a new project that I can build upon as I learn.  My project is a place to store information on client links and network information.

  • Create Project :: composer create-project laravel/laravel folder_name
  • Add new project url to homestead  :: mate ~/.homestead
    • When updating the Homestead.yaml File, you need to run “homestead up –provision” to reload the Yaml file.
  • Add URL to the Local Hosts File  ::  sudo nano /etc/hosts
  • Start up Homestead with  :: homestead up
  • If new settings where added to homestead, you should use :: homestead up –provision  (so it reloads the new settings from the homestead file.)
  • Run composer to update laravel first setup  ::  Composer install

 

Day 005 – Rewind

It was a late night last night, even though I work up a the usual time, I had to run tasks and take care of the kid.  So I am back, in the evening to write about some updates.

I watched a few more items in Jeffry ways Intro to Laravel.  The write up of the views, routes, and blade(template) engine is more confusing then I would have imagined.  (Compared to Rails)  But I see the form and practice is what would make it easier.

Next I want to explore are using Artisan commands to build the pages required for the app. I almost feel like I should prep a layout for a first project instead of using these lesson apps. If I decide on going a app route, then I really need to get Git up and running.

Day 004 – Messy

This morning I have been playing around with the Laravel template/file locations.  This is a bit different then Rails, but close.  Laravel seams a bit messy then Rails.  It still taking time to understand the full layout of how things are working.  I also don’t like all the different components for getting the environment running.  In addition to the commands seam to be in left field.  Time will tell and practice will help.  Maybe there is a cheat sheet out there.  http://cheats.jesse-obrien.ca/   Not sure if this helps…

FYI, With my setup of not having the right PHP on my local mac, you need to run any “php artisan” with the app directory in vagrant by homestead ssh into it.

I am at the point now to test our a database connection in vagrant.  the plan would be to make a table for pages to be used in the example project.