Hi Finally manged to find a shared host that could install October and was running PHP5.4.

This brings up a new issue for me. How to do some sort of version control whille both being able to change the code at the host via the backend and via the IDE (netbeans). Basically, when ever I change something from the backend, like adding a page or moving a plugin-script around the files changes, however this is not reflected in the IDE. Additionally I can, at the IDE change the pages without it being reflected at the backend/frontend at the live server.

My thoughts was something like only doing version control at my IDE on the plugin's and then pray nothing bad happends at my host-site. Still, it seems a bit dodgy.

How do you guys use a version control system that still enables you to use both backend and IDE editing.

(note: Yes, I should have a dedicated development setup and a dedicated live server. However, I am a hobby programmer and am still finding it very complicated working with diffrent envioments. Though, if thats the only solution and then using something like Git, then I guess that's what I have to do)

Thanks

Søren

Any ideas?

I think you're going to need some sort of local development, as that works best with October given the multiple ways of editing pages. I don't have a live site using October yet so other people may have a better workflow.

Local Development is done using a Vagrant box, which I have configured using puphpet. That allows me to have a local server with the files on the server synchronised with a local copy automatically. I've used NFS as the technology for that because I don't use windows and I had some issues with symfony in a previous project. I use git as my Version Control System (VCS). I use PhpStorm as my IDE. When a file is changed on either side (either through my IDE or through the backend) it is almost instantly reflected on both sides.

That's what works for me.

@benfreke: is it possible to get your 'puphpet' config.yaml file? i'm having a bit of trouble with my puphpet instance.

I know i am resurrecting an old thread here. I am new to Source controlling with a VM dev environment and I am trying to start a project where I am using Vagrant to setup an environment with October CMS has someone made a guide on how to do this yet?

Vagrant will give you headaches. Use Laravel Valet for local dev.

This guide on Setting up a local environment with October CMS will explain everything you need

Last updated 7 years ago

There is some controversial decisions in that guide. Nothing wrong with it but I'd personally be recommending different things.

But kudos to leader internet for taking the time to write the guides, nice work :)

If you're on a Mac, docker-compose is technically a better solution (valet is easier for beginners though), definitely better on Windows and I'd stick with Vagrant on Linux.

I agree with benfreke. docker = good, even on local and "docker for windows" getting pretty good now-a-days.